GHSA-f7f6-9jq7-3rqj — estree-util-value-to-estr…
Fix: remcohaszing/estree-util-value-to-estree@d0c394fGHSA-f7f6-9jq7-3rqj is a CWE-1321 vulnerability in estree-util-value-to-estree. A fix is available for estree-util-value-to-estree — see the affected versions and patch details below.
estree-util-value-to-estree allows prototype pollution in generated ESTree
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f7f6-9jq7-3rqj.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
estree-util-value-to-estreenpmDescription
Impact
When generating an ESTree from a value with a property named __proto__, valueToEstree would generate an object that specifies a prototype instead.
Example:
import { generate } from 'astring'
import { valueToEstree } from 'estree-util-value-to-estree'
const estree = valueToEstree({
['__proto__']: {}
})
const code = generate(estree)
console.log(code)
Output:
{
"__proto__": {}
}
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | estree-util-value-to-estree | all versions | 3.3.3npm install estree-util-value-to-estree@3.3.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for estree-util-value-to-estree, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update estree-util-value-to-estree to 3.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f7f6-9jq7-3rqj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f7f6-9jq7-3rqj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f7f6-9jq7-3rqj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f7f6-9jq7-3rqj in your dependencies?
O3 Security finds GHSA-f7f6-9jq7-3rqj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.