#1561

Accepted risk: deepmerge prototype poisoning (CVE-2026-93753), no patched release

Openashcoftopened 18d ago

Tracking issue for the accepted-risk dismissal of Dependabot alert #35.

Alert

FieldValue
Packagedeepmerge (npm), transitive, development scope
AdvisoryGHSA-gcqx-w48m-w2h4 / CVE-2026-93753
SeverityLow (CVSS 3.1 = 5.3)
Affected range>= 4.2.0, <= 4.3.1
Patched versionNone

Why it cannot be fixed in this repository

  • 4.3.1 is the latest published deepmerge (46 versions; no 4.3.2 or 5.x exists).
  • The upstream fix, TehShrike/deepmerge#286, is still open and unmerged, and master does not carry it.
  • pnpm audit --fix reports "No fixes were made".
  • Pinning below the affected range would be worse, not better. deepmerge 4.1.2 permits the classic __proto__ vector to set the returned object's prototype, which 4.3.1's guard blocks; it would also violate jest-config's ^4.3.1 requirement.

Why the risk is tolerable here

  • Not shipped. deepmerge is absent from the production bundles in js/. It arrives only through the Jest toolchain: jest-config@30.5.2 -> deepmerge ^4.3.1, pulled in by jest, @vue/vue3-jest and jest-watch-typeahead.
  • Not reachable. Dependabot reports the code as not reachable (reachability: disabled).
  • Not exercised. The bypass needs merge(defaults, JSON.parse(attackerBody)) where defaults is a null-prototype object or holds a null placeholder. jest-config only merges its own defaults with local overrides; it never merges untrusted request data.

What to do

Revisit when upstream publishes a release containing the fix, then bump via the normal dependency flow. This was already noted in commit 0e560c3a7.


This issue was created by an AI agent (OpenHands) on behalf of the user.

Activity

0

No activity yet.