jest-dom-5.17.0.tgz: 4 vulnerabilities (highest severity is: 8.1) #8

Vulnerable Library - jest-dom-5.17.0.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /node_modules/lodash/package.json

CVE-2026-4800

Vulnerable Library - lodash-4.17.21.tgz

Lodash modular utilities.

Library home page: https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /node_modules/lodash/package.json

Dependency Hierarchy:

• jest-dom-5.17.0.tgz (Root Library)
  • ❌ lodash-4.17.21.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

The fix for CVE-2021-23337 added validation for the variable option in _.template but did not apply the same validation to options.imports key names, and both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in, so if Object.prototype has been polluted by another vector the polluted keys are copied into the imports object and passed to Function(). The issue is fixed in 4.18.1 for lodash, lodash-es, lodash-amd, and lodash.template. As a workaround, do not pass untrusted input as key names in options.imports; use only developer-controlled, static key names.

Publish Date: 2026-03-31

URL: CVE-2026-4800

CVSS 3 Score Details (8.1)

Base Score Metrics:

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

Suggested Fix

Type: Upgrade version

Origin: GHSA-r5fr-rjxr-66jc

Release Date: 2026-03-31

Fix Resolution: lodash - 4.18.0

Step up your Open Source Security Game with Mend here

CVE-2025-13465

Vulnerable Library - lodash-4.17.21.tgz

Lodash modular utilities.

Library home page: https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /node_modules/lodash/package.json

Dependency Hierarchy:

• jest-dom-5.17.0.tgz (Root Library)
  • ❌ lodash-4.17.21.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

The _.unset and _.omit functions in Lodash are vulnerable to prototype pollution. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. The issue is patched from 4.17.23 to 4.18.0 depending on the package: lodash, lodash-es, and lodash-amd in 4.17.23, and the standalone lodash.unset and lodash.omit packages in 4.18.0.

Publish Date: 2026-01-21

URL: CVE-2025-13465

CVSS 3 Score Details (7.2)

Base Score Metrics:

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

Suggested Fix

Type: Upgrade version

Origin: GHSA-xxjr-mmjv-4gpg

Release Date: 2026-01-21

Fix Resolution: lodash - 4.17.23

Step up your Open Source Security Game with Mend here

CVE-2026-2950

Vulnerable Library - lodash-4.17.21.tgz

Lodash modular utilities.

Library home page: https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /node_modules/lodash/package.json

Dependency Hierarchy:

• jest-dom-5.17.0.tgz (Root Library)
  • ❌ lodash-4.17.21.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

The _.unset and _.omit functions in Lodash are vulnerable to prototype pollution. The fix for CVE-2025-13465 only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. The issue is patched from 4.18.0 to 4.18.1 depending on the package: lodash, lodash-es, and lodash-amd in 4.18.1, and the standalone lodash.unset and lodash.omit packages in 4.18.0.

Publish Date: 2026-03-31

URL: CVE-2026-2950

CVSS 3 Score Details (6.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: Low
  • Availability Impact: Low

Suggested Fix

Type: Upgrade version

Origin: GHSA-xxjr-mmjv-4gpg

Release Date: 2026-03-31

Fix Resolution (lodash): 4.17.23

Direct dependency fix Resolution (@⁠testing-library/jest-dom): 6.4.3

Step up your Open Source Security Game with Mend here

CVE-2025-27789

Vulnerable Library - runtime-7.24.5.tgz

Library home page: https://registry.npmjs.org/@⁠babel/runtime/-/runtime-7.24.5.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /node_modules/@⁠babel/runtime/package.json

Dependency Hierarchy:

• jest-dom-5.17.0.tgz (Root Library)
  • ❌ runtime-7.24.5.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 to compile regular expression named capturing groups, Babel will generate a polyfill for the ".replace" method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to ".replace"). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the ".replace" method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of ".replace". This problem has been fixed in "@⁠babel/helpers" and "@⁠babel/runtime" 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on "@⁠babel/helpers", and instead depend on "@⁠babel/core" (which itself depends on "@⁠babel/helpers"). Upgrading to "@⁠babel/core" 7.26.10 is not required, but it guarantees use of a new enough "@⁠babel/helpers" version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.

Publish Date: 2025-03-11

URL: CVE-2025-27789

CVSS 3 Score Details (6.2)

Base Score Metrics:

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

Suggested Fix

Type: Upgrade version

Origin: GHSA-968p-4wvh-cqc8

Release Date: 2025-03-11

Fix Resolution (@⁠babel/runtime): 7.26.10

Direct dependency fix Resolution (@⁠testing-library/jest-dom): 6.0.0

Step up your Open Source Security Game with Mend here