npm-10.7.0.tgz: 15 vulnerabilities (highest severity is: 8.8)

[mend-bolt-for-github]

Vulnerable Library - npm-10.7.0.tgz

Library home page: https://registry.npmjs.org/npm/-/npm-10.7.0.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (npm version)	Remediation Possible**
CVE-2026-23950	High	8.8	tar-6.2.1.tgz	Transitive	10.9.6	❌
CVE-2026-24842	High	8.2	tar-6.2.1.tgz	Transitive	10.9.6	❌
CVE-2026-27904	High	7.5	minimatch-9.0.4.tgz	Transitive	10.8.0	❌
CVE-2026-27903	High	7.5	minimatch-9.0.4.tgz	Transitive	N/A*	❌
CVE-2026-26996	High	7.5	minimatch-9.0.4.tgz	Transitive	N/A*	❌
CVE-2025-64756	High	7.5	glob-10.3.12.tgz	Transitive	10.8.0	❌
CVE-2024-21538	High	7.5	cross-spawn-7.0.3.tgz	Transitive	11.6.3	❌
CVE-2026-31802	High	7.1	tar-6.2.1.tgz	Transitive	N/A*	❌
CVE-2026-29786	High	7.1	tar-6.2.1.tgz	Transitive	N/A*	❌
CVE-2026-26960	High	7.1	tar-6.2.1.tgz	Transitive	10.9.6	❌
CVE-2026-23745	High	7.1	tar-6.2.1.tgz	Transitive	N/A*	❌
CVE-2026-0775	High	7.0	npm-10.7.0.tgz	Direct	N/A	❌
CVE-2026-33750	Medium	6.5	brace-expansion-2.0.1.tgz	Transitive	N/A*	❌
CVE-2026-24001	Medium	5.3	diff-5.2.0.tgz	Transitive	N/A*	❌
CVE-2025-5889	Low	3.1	brace-expansion-2.0.1.tgz	Transitive	10.8.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-23950

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the "path-reservations" system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., "ß" and "ss"), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a "PathReservations" system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using "NFD" Unicode normalization (in which "ß" and "ss" are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which "ß" causes an inode collision with "ss")). This enables an attacker to circumvent internal parallelization locks ("PathReservations") using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates "path-reservations.js" to use a normalization form that matches the target filesystem's behavior (e.g., "NFKD"), followed by first "toLocaleLowerCase('en')" and then "toLocaleUpperCase('en')". As a workaround, users who cannot upgrade promptly, and who are programmatically using "node-tar" to extract arbitrary tarball data should filter out all "SymbolicLink" entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue.

Publish Date: 2026-01-20

URL: CVE-2026-23950

CVSS 3 Score Details (8.8)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-r6q2-hw4h-h46w

Release Date: 2026-01-20

Fix Resolution (tar): 7.5.4

Direct dependency fix Resolution (npm): 10.9.6

Step up your Open Source Security Game with Mend here

CVE-2026-24842

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar,a Tar for Node.js, contains a vulnerability in versions prior to 7.5.7 where the security check for hardlink entries uses different path resolution semantics than the actual hardlink creation logic. This mismatch allows an attacker to craft a malicious TAR archive that bypasses path traversal protections and creates hardlinks to arbitrary files outside the extraction directory. Version 7.5.7 contains a fix for the issue.

Publish Date: 2026-01-28

URL: CVE-2026-24842

CVSS 3 Score Details (8.2)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-01-28

Fix Resolution (tar): 7.5.7

Direct dependency fix Resolution (npm): 10.9.6

Step up your Open Source Security Game with Mend here

CVE-2026-27904

Vulnerable Library - minimatch-9.0.4.tgz

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

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ minimatch-9.0.4.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

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 (npm): 10.8.0

Step up your Open Source Security Game with Mend here

CVE-2026-27903

Vulnerable Library - minimatch-9.0.4.tgz

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

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ minimatch-9.0.4.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

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 - v8.0.6,https://github.com/isaacs/minimatch.git - v10.2.3,https://github.com/isaacs/minimatch.git - v5.1.8,https://github.com/isaacs/minimatch.git - v7.4.8,https://github.com/isaacs/minimatch.git - v4.2.5,https://github.com/isaacs/minimatch.git - v9.0.7,https://github.com/isaacs/minimatch.git - v6.2.2

Step up your Open Source Security Game with Mend here

CVE-2026-26996

Vulnerable Library - minimatch-9.0.4.tgz

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

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ minimatch-9.0.4.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

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 - v8.0.5,https://github.com/isaacs/minimatch.git - v4.2.4,https://github.com/isaacs/minimatch.git - v9.0.6,https://github.com/isaacs/minimatch.git - v3.1.3,https://github.com/isaacs/minimatch.git - v6.2.1,https://github.com/isaacs/minimatch.git - v7.4.7

Step up your Open Source Security Game with Mend here

CVE-2025-64756

Vulnerable Library - glob-10.3.12.tgz

Library home page: https://registry.npmjs.org/glob/-/glob-10.3.12.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ glob-10.3.12.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

Glob matches files using patterns the shell uses. Starting in version 10.2.0 and prior to versions 10.5.0 and 11.1.0, the glob CLI contains a command injection vulnerability in its -c/--cmd option that allows arbitrary command execution when processing files with malicious names. When glob -c are used, matched filenames are passed to a shell with shell: true, enabling shell metacharacters in filenames to trigger command injection and achieve arbitrary code execution under the user or CI account privileges. This issue has been patched in versions 10.5.0 and 11.1.0.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2025-11-17

URL: CVE-2025-64756

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: Low
  • 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-5j98-mcp5-4vw2

Release Date: 2025-11-17

Fix Resolution (glob): 10.5.0

Direct dependency fix Resolution (npm): 10.8.0

Step up your Open Source Security Game with Mend here

CVE-2024-21538

Vulnerable Library - cross-spawn-7.0.3.tgz

Cross platform child_process#spawn and child_process#spawnSync

Library home page: https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • glob-10.3.12.tgz
    • foreground-child-3.1.1.tgz
      • ❌ cross-spawn-7.0.3.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

Versions of the package cross-spawn before 6.0.6, from 7.0.0 and before 7.0.5 are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.

Publish Date: 2024-11-08

URL: CVE-2024-21538

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: https://nvd.nist.gov/vuln/detail/CVE-2024-21538

Release Date: 2024-11-08

Fix Resolution (cross-spawn): 7.0.5

Direct dependency fix Resolution (npm): 11.6.3

Step up your Open Source Security Game with Mend here

CVE-2026-31802

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar is a full-featured Tar for Node.js. Prior to version 7.5.11, tar (npm) can be tricked into creating a symlink that points outside the extraction directory by using a drive-relative symlink target such as C:../../../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This vulnerability is fixed in 7.5.11.

Publish Date: 2026-03-09

URL: CVE-2026-31802

CVSS 3 Score Details (7.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-03-09

Fix Resolution: https://github.com/isaacs/node-tar.git - v7.5.11

Step up your Open Source Security Game with Mend here

CVE-2026-29786

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar is a full-featured Tar for Node.js. Prior to version 7.5.10, tar can be tricked into creating a hardlink that points outside the extraction directory by using a drive-relative link target such as C:../target.txt, which enables file overwrite outside cwd during normal tar.x() extraction. This issue has been patched in version 7.5.10.

Publish Date: 2026-03-07

URL: CVE-2026-29786

CVSS 3 Score Details (7.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-03-07

Fix Resolution: https://github.com/isaacs/node-tar.git - v7.5.10

Step up your Open Source Security Game with Mend here

CVE-2026-26960

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar is a full-featured Tar for Node.js. When using default options in versions 7.5.7 and below, an attacker-controlled archive can create a hardlink inside the extraction directory that points to a file outside the extraction root, enabling arbitrary file read and write as the extracting user. Severity is high because the primitive bypasses path protections and turns archive extraction into a direct filesystem access primitive. This issue has been fixed in version 7.5.8.

Publish Date: 2026-02-20

URL: CVE-2026-26960

CVSS 3 Score Details (7.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-02-18

Fix Resolution (tar): 7.5.8

Direct dependency fix Resolution (npm): 10.9.6

Step up your Open Source Security Game with Mend here

CVE-2026-23745

Vulnerable Library - tar-6.2.1.tgz

Library home page: https://registry.npmjs.org/tar/-/tar-6.2.1.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • ❌ tar-6.2.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3.

Publish Date: 2026-01-16

URL: CVE-2026-23745

CVSS 3 Score Details (7.1)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-01-16

Fix Resolution: https://github.com/isaacs/node-tar.git - v7.5.3

Step up your Open Source Security Game with Mend here

CVE-2026-0775

Vulnerable Library - npm-10.7.0.tgz

Library home page: https://registry.npmjs.org/npm/-/npm-10.7.0.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• ❌ npm-10.7.0.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

npm cli Incorrect Permission Assignment Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of npm cli. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
The specific flaw exists within the handling of modules. The application loads modules from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of a target user. Was ZDI-CAN-25430.

Publish Date: 2026-01-23

URL: CVE-2026-0775

CVSS 3 Score Details (7.0)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Step up your Open Source Security Game with Mend here

CVE-2026-33750

Vulnerable Library - brace-expansion-2.0.1.tgz

Brace expansion as known from sh/bash

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

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • minimatch-9.0.4.tgz
    • ❌ brace-expansion-2.0.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

Impact 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. The loop in question: https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L184 "test()" is one of https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L107-L113 The increment is computed as "Math.abs(0) = 0", so the loop variable never advances. On a test machine, the process hangs for about 3.5 seconds and allocates roughly 1.9 GB of memory before throwing a "RangeError". Setting max to any value has no effect because the limit is only checked at the output combination step, not during sequence generation. This affects any application that passes untrusted strings to expand(), or by error sets a step value of "0". That includes tools built on minimatch/glob that resolve patterns from CLI arguments or config files. The input needed is just 10 bytes. Patches Upgrade to versions - 5.0.5+ A step increment of 0 is now sanitized to 1, which matches bash behavior. Workarounds 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

Origin: GHSA-f886-m6hf-6m8v

Release Date: 2026-03-26

Fix Resolution: brace-expansion - 5.0.5,brace-expansion - 2.0.3,brace-expansion - 1.1.13,brace-expansion - 3.0.2

Step up your Open Source Security Game with Mend here

CVE-2026-24001

Vulnerable Library - diff-5.2.0.tgz

Library home page: https://registry.npmjs.org/diff/-/diff-5.2.0.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • libnpmdiff-6.1.1.tgz
    • ❌ diff-5.2.0.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

jsdiff is a JavaScript text differencing implementation. Prior to versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1, attempting to parse a patch whose filename headers contain the line break characters "\r", "\u2028", or "\u2029" can cause the "parsePatch" method to enter an infinite loop. It then consumes memory without limit until the process crashes due to running out of memory. Applications are therefore likely to be vulnerable to a denial-of-service attack if they call "parsePatch" with a user-provided patch as input. A large payload is not needed to trigger the vulnerability, so size limits on user input do not provide any protection. Furthermore, some applications may be vulnerable even when calling "parsePatch" on a patch generated by the application itself if the user is nonetheless able to control the filename headers (e.g. by directly providing the filenames of the files to be diffed). The "applyPatch" method is similarly affected if (and only if) called with a string representation of a patch as an argument, since under the hood it parses that string using "parsePatch". Other methods of the library are unaffected. Finally, a second and lesser interdependent bug - a ReDOS - also exhibits when those same line break characters are present in a patch's patch header (also known as its "leading garbage"). A maliciously-crafted patch header of length n can take "parsePatch" O(n³) time to parse. Versions 8.0.3, 5.2.2, 4.0.4, and 3.5.1 contain a fix. As a workaround, do not attempt to parse patches that contain any of these characters: "\r", "\u2028", or "\u2029".
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2026-01-22

URL: CVE-2026-24001

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

Release Date: 2026-01-22

Fix Resolution: https://github.com/kpdecker/jsdiff.git - v4.0.4,https://github.com/kpdecker/jsdiff.git - v5.2.2,https://github.com/kpdecker/jsdiff.git - v8.0.3

Step up your Open Source Security Game with Mend here

CVE-2025-5889

Vulnerable Library - brace-expansion-2.0.1.tgz

Brace expansion as known from sh/bash

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

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• npm-10.7.0.tgz (Root Library)
  • minimatch-9.0.4.tgz
    • ❌ brace-expansion-2.0.1.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

A vulnerability was found in juliangruber brace-expansion up to 1.1.11. It has been rated as problematic. Affected by this issue is the function expand of the file index.js. The manipulation leads to inefficient regular expression complexity. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is a5b98a4f30d7813266b221435e1eaaf25a1b0ac5. It is recommended to apply a patch to fix this issue.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2025-06-09

URL: CVE-2025-5889

CVSS 3 Score Details (3.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: Low
  • 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-v6h2-p8h4-qcjw

Release Date: 2025-06-09

Fix Resolution (brace-expansion): 2.0.2

Direct dependency fix Resolution (npm): 10.8.0

Step up your Open Source Security Game with Mend here