{"answers":{"affected":"2 open source packages ship an affected version, including estree-util-value-to-estree.","exploited":"There is no known exploitation of CVE-2025-32014 in the wild and no public exploit code.","fix":"Upgrade estree-util-value-to-estree to 3.3.3 or later.","what":"CVE-2025-32014 is a medium-severity vulnerability in remcohaszing estree-util-value-to-estree, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32014 and fix it if it is affected.\n\nWhat it is: CVE-2025-32014 is a medium-severity vulnerability in remcohaszing estree-util-value-to-estree, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32014 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- estree-util-value-to-estree (npm): affected all versions; fixed in 3.3.3\n- estree-util-value-to-estree (npm): affected all versions; fixed in 3.3.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32014/ (Markdown: https://insights.sbomify.com/CVE-2025-32014/index.md)","id":"CVE-2025-32014","markdown":"https://insights.sbomify.com/CVE-2025-32014/index.md","name":"CVE-2025-32014","record":{"aliases":["CLSA-2026-1784943105","GHSA-f7f6-9jq7-3rqj","MINI-2mgx-9rqc-rhm5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"none","summary":"Prototype pollution in estree-util-value-to-estree allows attackers to manipulate object prototypes, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"estree-util-value-to-estree converts a JavaScript value to an ESTree expression. When generating an ESTree from a value with a property named __proto__, valueToEstree would generate an object that specifies a prototype instead. This vulnerability is fixed in 3.3.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"estree-util-value-to-estree allows prototype pollution in generated ESTree","id":"CVE-2025-32014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"FreshRSS vulnerable to Cross-site Scripting by embedding \u003cscript\u003e tag inside \u003ciframe srcdoc\u003e","id":"CVE-2025-32015"},"packages":[{"ecosystem":"npm","fixed":["3.3.3"],"introduced":["0"],"last_affected":[],"package":"estree-util-value-to-estree","purl":null,"source":"GHSA-f7f6-9jq7-3rqj"},{"ecosystem":"npm","fixed":["3.3.3"],"introduced":["0"],"last_affected":[],"package":"estree-util-value-to-estree","purl":"pkg:npm/estree-util-value-to-estree","source":"GHSA-f7f6-9jq7-3rqj"}],"prev":{"headline":"Server-Side Request Forgery via LNURL Authentication Callback in LNbits Lightning Network Payment System","id":"CVE-2025-32013"},"products":["estree-util-value-to-estree"],"published":"2025-04-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-07","vendors":["remcohaszing"]},"summary":"Prototype pollution in estree-util-value-to-estree allows attackers to manipulate object prototypes, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-32014/"}