estree-util-value-to-estree allows prototype pollution in generated ESTree

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source

EPSS

• CVE-2025-32014: 0.46% estimated exploitation activity in the next 30 days; percentile 39.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When generating an ESTree from a value with a property named proto, valueToEstree would generate an object that specifies a prototype instead. Example: Output: Patches This was fixed in version 3.3.3. Workarounds If you control the input, don’t specify a property named proto. If you don’t control the output, strip any properties named proto before passing it to valueToEstree.

Published by the source

7 Apr 2025, 19:09 UTC

Last modified by the source

7 Apr 2025, 19:57 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f7f6-9jq7-3rqj

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f7f6-9jq7-3rqj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-32014

Advisory: estree-util-value-to-estree allows prototype pollution in generated ESTree
IDs: CVE-2025-32014, GHSA-f7f6-9jq7-3rqj
Record: https://patchnext.com/advisories/cve-2025-32014 (revision 3, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: estree-util-value-to-estree 3.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm estree-util-value-to-estree: affected < 3.3.3; fixed in 3.3.3

## Suggested inspection (read-only)
- `npm ls estree-util-value-to-estree --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on estree-util-value-to-estree.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f7f6-9jq7-3rqj (OSV record GHSA-f7f6-9jq7-3rqj lists affected ranges: npm estree-util-value-to-estree >=0 <3.3.3 (fixed))
- Verified: https://github.com/advisories/GHSA-f7f6-9jq7-3rqj (GitHub-reviewed advisory GHSA-f7f6-9jq7-3rqj lists affected ranges: npm estree-util-value-to-estree >=0 <3.3.3)

Commands are suggestions: review each one before running it.