#1561
Accepted risk: deepmerge prototype poisoning (CVE-2026-93753), no patched release
Tracking issue for the accepted-risk dismissal of Dependabot alert #35.
Alert
| Field | Value |
|---|---|
| Package | deepmerge (npm), transitive, development scope |
| Advisory | GHSA-gcqx-w48m-w2h4 / CVE-2026-93753 |
| Severity | Low (CVSS 3.1 = 5.3) |
| Affected range | >= 4.2.0, <= 4.3.1 |
| Patched version | None |
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
masterdoes not carry it. pnpm audit --fixreports "No fixes were made".- Pinning below the affected range would be worse, not better.
deepmerge4.1.2 permits the classic__proto__vector to set the returned object's prototype, which 4.3.1's guard blocks; it would also violatejest-config's^4.3.1requirement.
Why the risk is tolerable here
- Not shipped.
deepmergeis absent from the production bundles injs/. It arrives only through the Jest toolchain:jest-config@30.5.2 -> deepmerge ^4.3.1, pulled in byjest,@vue/vue3-jestandjest-watch-typeahead. - Not reachable. Dependabot reports the code as not reachable (
reachability: disabled). - Not exercised. The bypass needs
merge(defaults, JSON.parse(attackerBody))wheredefaultsis a null-prototype object or holds anullplaceholder.jest-configonly 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
0No activity yet.