vcr-sdk-1.3.0.tgz: 7 vulnerabilities (highest severity is: 9.8)

[mend-for-github-com]

Vulnerable Library - vcr-sdk-1.3.0.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (vcr-sdk version)	Remediation Possible**
CVE-2026-41907	Critical	9.8	uuid-8.3.2.tgz	Transitive	N/A*	❌
CVE-2026-4867	High	7.5	path-to-regexp-0.1.12.tgz	Transitive	N/A*	❌
CVE-2026-27904	High	7.5	minimatch-9.0.5.tgz	Transitive	1.4.0	✅
CVE-2026-27903	High	7.5	minimatch-9.0.5.tgz	Transitive	N/A*	❌
CVE-2026-26996	High	7.5	minimatch-9.0.5.tgz	Transitive	N/A*	❌
CVE-2026-33750	Medium	6.5	brace-expansion-2.0.2.tgz	Transitive	N/A*	❌
CVE-2026-8723	Medium	5.3	qs-6.14.2.tgz	Transitive	1.4.0	✅

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-41907

Vulnerable Library - uuid-8.3.2.tgz

RFC4122 (v1, v4, and v5) UUIDs

Library home page: https://registry.npmjs.org/uuid/-/uuid-8.3.2.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • ❌ uuid-8.3.2.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

uuid is for the creation of RFC9562 (formerly RFC4122) UUIDs. Prior to 14.0.0, v3, v5, and v6 accept external output buffers but do not reject out-of-range writes (small buf or large offset). This allows silent partial writes into caller-provided buffers. This vulnerability is fixed in 14.0.0.

Publish Date: 2026-04-24

URL: CVE-2026-41907

CVSS 3 Score Details (9.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-w5hq-g745-h8pq

Release Date: 2026-04-24

Fix Resolution: https://github.com/uuidjs/uuid.git - v11.1.1,https://github.com/uuidjs/uuid.git - v12.0.1,https://github.com/uuidjs/uuid.git - v13.0.1

CVE-2026-4867

Vulnerable Library - path-to-regexp-0.1.12.tgz

Express style path to RegExp utility

Library home page: https://registry.npmjs.org/path-to-regexp/-/path-to-regexp-0.1.12.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json,/tutorials/video-javascript-multiparty_archiving/project/package.json,/tutorials/video-javascript-debugging/project/package.json,/tutorials/video-javascript-archive_layouts/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • express-4.22.1.tgz
    • ❌ path-to-regexp-0.1.12.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

Impact:
A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b-:c or /:a-:b-:c-:d. The backtrack protection added in path-to-regexp@0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, so capture groups overlap and cause catastrophic backtracking.
Patches:
Upgrade to path-to-regexp@0.1.13
Custom regex patterns in route definitions (e.g., /:a-:b([^-/]+)-:c([^-/]+)) are not affected because they override the default capture group.
Workarounds:
All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b-:c to /:a-:b([^-/]+)-:c([^-/]+).
If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length.

Publish Date: 2026-03-26

URL: CVE-2026-4867

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-37ch-88jc-xwx2

Release Date: 2026-03-26

Fix Resolution: path-to-regexp - 0.1.13

CVE-2026-27904

Vulnerable Library - minimatch-9.0.5.tgz

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • glob-10.5.0.tgz
    • ❌ minimatch-9.0.5.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested "()" extglobs produce regexps with nested unbounded quantifiers (e.g. "(?:(?:a|b))"), which exhibit catastrophic backtracking in V8. With a 12-byte pattern "(((a|b)))" and an 18-byte non-matching input, "minimatch()" stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default "minimatch()" API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects "+()" extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue.

Publish Date: 2026-02-26

URL: CVE-2026-27904

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-23c5-xmqv-rm74

Release Date: 2026-02-26

Fix Resolution (minimatch): 9.0.7

Direct dependency fix Resolution (@⁠vonage/vcr-sdk): 1.4.0

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2026-27903

Vulnerable Library - minimatch-9.0.5.tgz

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • glob-10.5.0.tgz
    • ❌ minimatch-9.0.5.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3, "matchOne()" performs unbounded recursive backtracking when a glob pattern contains multiple non-adjacent "**" (GLOBSTAR) segments and the input path does not match. The time complexity is O(C(n, k)) -- binomial -- where "n" is the number of path segments and "k" is the number of globstars. With k=11 and n=30, a call to the default "minimatch()" API stalls for roughly 5 seconds. With k=13, it exceeds 15 seconds. No memoization or call budget exists to bound this behavior. Any application where an attacker can influence the glob pattern passed to "minimatch()" is vulnerable. The realistic attack surface includes build tools and task runners that accept user-supplied glob arguments (ESLint, Webpack, Rollup config), multi-tenant systems where one tenant configures glob-based rules that run in a shared process, admin or developer interfaces that accept ignore-rule or filter configuration as globs, and CI/CD pipelines that evaluate user-submitted config files containing glob patterns. An attacker who can place a crafted pattern into any of these paths can stall the Node.js event loop for tens of seconds per invocation. The pattern is 56 bytes for a 5-second stall and does not require authentication in contexts where pattern input is part of the feature. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3 fix the issue.

Publish Date: 2026-02-26

URL: CVE-2026-27903

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-7r86-cg39-jmmj

Release Date: 2026-02-26

Fix Resolution: https://github.com/isaacs/minimatch.git - v3.1.3,https://github.com/isaacs/minimatch.git - v4.2.5,https://github.com/isaacs/minimatch.git - v6.2.2,https://github.com/isaacs/minimatch.git - v10.2.3,https://github.com/isaacs/minimatch.git - v5.1.8,https://github.com/isaacs/minimatch.git - v9.0.7,https://github.com/isaacs/minimatch.git - v7.4.8,https://github.com/isaacs/minimatch.git - v8.0.6

CVE-2026-26996

Vulnerable Library - minimatch-9.0.5.tgz

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • glob-10.5.0.tgz
    • ❌ minimatch-9.0.5.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions prior to 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6 are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS.
This issue has been fixed in versions 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2026-02-20

URL: CVE-2026-26996

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-3ppc-4f35-3m26

Release Date: 2026-02-19

Fix Resolution: https://github.com/isaacs/minimatch.git - v10.2.1,https://github.com/isaacs/minimatch.git - v5.1.7,https://github.com/isaacs/minimatch.git - v4.2.4,https://github.com/isaacs/minimatch.git - v3.1.3,https://github.com/isaacs/minimatch.git - v8.0.5,https://github.com/isaacs/minimatch.git - v9.0.6,https://github.com/isaacs/minimatch.git - v6.2.1,https://github.com/isaacs/minimatch.git - v7.4.7

CVE-2026-33750

Vulnerable Library - brace-expansion-2.0.2.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz

Path to dependency file: /tutorials/vonage_video_react_app-feature-config/project/package.json

Path to vulnerable library: /tutorials/vonage_video_react_app-feature-config/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • glob-10.5.0.tgz
    • minimatch-9.0.5.tgz
      • ❌ brace-expansion-2.0.2.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13, a brace pattern with a zero step value (e.g., "{1..2..0}") causes the sequence generation loop to run indefinitely, making the process hang for seconds and allocate heaps of memory. Versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13 fix the issue. As a workaround, sanitize strings passed to "expand()" to ensure a step value of "0" is not used.

Publish Date: 2026-03-27

URL: CVE-2026-33750

CVSS 3 Score Details (6.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-03-27

Fix Resolution: https://github.com/juliangruber/brace-expansion.git - v2.0.3,https://github.com/juliangruber/brace-expansion.git - v3.0.2,https://github.com/juliangruber/brace-expansion.git - v5.0.5,https://github.com/juliangruber/brace-expansion.git - v1.1.13

CVE-2026-8723

Vulnerable Library - qs-6.14.2.tgz

A querystring parser that supports nesting and arrays, with a depth limit

Library home page: https://registry.npmjs.org/qs/-/qs-6.14.2.tgz

Path to dependency file: /tutorials/video-javascript-debugging/project/package.json

Path to vulnerable library: /tutorials/video-javascript-debugging/project/package.json,/tutorials/video_learning_server-node-deploy/project/package.json,/tutorials/vonage_video_react_app-feature-config/project/package.json,/tutorials/video-javascript-signaling/project/package.json,/tutorials/video-javascript-multiparty_archiving/project/package.json,/tutorials/video-javascript-archive_layouts/project/package.json

Dependency Hierarchy:

• vcr-sdk-1.3.0.tgz (Root Library)
  • express-4.22.1.tgz
    • ❌ qs-6.14.2.tgz (Vulnerable Library)

Found in HEAD commit: 4e2cf9adce70dc70d3b4bb66d02e43c4a1afa182

Found in base branch: main

Vulnerability Details

Summary
"qs.stringify" throws "TypeError" when called with "arrayFormat: 'comma'" and "encodeValuesOnly: true" on an array containing "null" or "undefined". The throw is synchronous and not handled by any of qs's null-related options ("skipNulls", "strictNullHandling").
Details
In the comma + "encodeValuesOnly" branch, "lib/stringify.js:145" mapped the array through the raw encoder before joining:
obj = utils.maybeMap(obj, encoder);
"utils.encode" ("lib/utils.js:195") reads "str.length" with no null guard, so a "null" or "undefined" element throws "TypeError". "skipNulls" and "strictNullHandling" are both checked in the per-element loop below this line and never get a chance to run.
Same class of bug as the filter-array path fixed in 0c180a4. The vulnerable shape of the comma + "encodeValuesOnly" branch was introduced in 4c4b23d ("encode comma values more consistently", PR #⁠463, 2023-01-19), first released in v6.11.1.
PoC
const qs = require('qs');
qs.stringify({ a: [null, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true });
qs.stringify({ a: [undefined, 'b'] }, { arrayFormat: 'comma', encodeValuesOnly: true });
qs.stringify({ a: [null] }, { arrayFormat: 'comma', encodeValuesOnly: true });
// TypeError: Cannot read properties of null (reading 'length')
// at encode (lib/utils.js:195:13)
// at Object.maybeMap (lib/utils.js:322:37)
// at stringify (lib/stringify.js:145:25)
Fix
"lib/stringify.js:145", applied in 21f80b3 on "main" and released as v6.15.2:

• obj = utils.maybeMap(obj, encoder);

• obj = utils.maybeMap(obj, function (v) {

• return v == null ? v : encoder(v);
  

• });
  "null" and "undefined" now pass through "maybeMap" unchanged and reach the "join(',')" step as-is. For "{ a: [null, 'b'] }" this produces "a=,b", matching the non-"encodeValuesOnly" comma path (which already joins before encoding and produces "a=%2Cb" for the same input). Single-element "[null]" arrays still collapse via the existing "obj.join(',') || null" and remain subject to "skipNulls" / "strictNullHandling" in the main loop.
  Affected versions
  ">=6.11.1 <6.15.2" — fixed in v6.15.2.
  The vulnerable code shape was introduced in 4c4b23d and first shipped in v6.11.1. Earlier versions — including all of 6.7.x, 6.8.x, 6.9.x, 6.10.x, and 6.11.0 — implemented the comma + "encodeValuesOnly" path differently (joining before encoding) and are not affected. Empirically verified across released versions.
  Impact
  Application code that calls "qs.stringify" with both "arrayFormat: 'comma'" and "encodeValuesOnly: true" (both non-default) on input that may contain a "null" or "undefined" array element will throw synchronously instead of producing a query string. In a typical Node.js HTTP framework (Express, Fastify, Koa, hapi) the sync throw is caught by the framework's error boundary and the affected request returns a 500; the worker process does not exit and subsequent requests are unaffected. The "kills the worker process" framing applies only to call sites outside a request-handler error boundary (background jobs, startup paths, stream pipelines) or to deployments with framework error handling explicitly disabled.
  The vulnerable input is a "null" or "undefined" entry inside an array; this is reachable from JSON request bodies or from application code constructing arrays from user input, but not from standard HTML form submissions (which produce strings or omitted fields, not literal "null").
  Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2026-05-16

URL: CVE-2026-8723

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-q8mj-m7cp-5q26

Release Date: 2026-05-16

Fix Resolution (qs): 6.15.2

Direct dependency fix Resolution (@⁠vonage/vcr-sdk): 1.4.0

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.