{"schema_version":"1.9.0","id":"CVE-2025-64718","published":"2025-11-13T15:32:44.634Z","modified":"2026-08-12T03:51:47.546304918Z","aliases":["GHSA-mh29-5h37-fv8m"],"related":["CGA-mfcv-6pv8-6v39","SUSE-SU-2026:20170-1","SUSE-SU-2026:20182-1","SUSE-SU-2026:20540-1","SUSE-SU-2026:20580-1","openSUSE-SU-2026:10036-1","openSUSE-SU-2026:11126-1","openSUSE-SU-2026:20117-1","openSUSE-SU-2026:20251-1"],"summary":"js-yaml has prototype pollution in merge (<<)","details":"js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).","affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/nodeca/js-yaml","events":[{"introduced":"0"},{"fixed":"9963d366dfbde0c69722452bcd40b41e7e4160a0"},{"introduced":"ee74ce4b4800282b2f23b776be7dc95dfe34db1c"},{"fixed":"cc482e775913e6625137572a3712d2826170e53a"},{"fixed":"383665ff4248ec2192d1274e934462bb30426879"},{"fixed":"5278870a17454fe8621dbd8c445c412529525266"}],"database_specific":{"cpe":"cpe:2.3:a:nodeca:js-yaml:*:*:*:*:*:node.js:*:*","extracted_events":[{"introduced":"0"},{"fixed":"3.14.2"},{"introduced":"4.0.0"},{"fixed":"4.1.1"}],"source":["CPE_RANGE","REFERENCES"]}}],"versions":["3.14.1","4.1.0","4.0.0","3.14.0","3.13.1","3.13.0","3.12.2","3.12.1","3.12.0","3.11.0","3.10.0","3.9.1","3.9.0","3.8.4","3.8.3","3.8.2","3.8.1","3.8.0","3.7.0","3.6.1","3.6.0","3.5.5","3.5.4","3.5.3","3.5.2","3.5.1","3.5.0","3.4.6","3.4.5","3.4.4","3.4.3","3.4.2","3.4.1","3.4.0","3.3.1","3.3.0","3.2.7","3.2.6","3.2.5","3.2.4","3.2.3","3.2.2","3.2.1","3.2.0","3.1.0","3.0.2","3.0.1","3.0.0","2.1.3","2.1.2","2.1.1","2.1.0","2.0.5","2.0.4","2.0.3","2.0.2","2.0.1","2.0.0","1.0.3","1.0.2","1.0.1","1.0.0","0.3.7","0.3.5","0.3.4","0.3.3","0.3.2","0.2.2","0.2.1","0.2.0","0.1.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-64718.json"}}],"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/64xxx/CVE-2025-64718.json"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-mh29-5h37-fv8m"},{"type":"ADVISORY","url":"https://github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8m"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-64718"},{"type":"REPORT","url":"https://github.com/nodeca/js-yaml/issues/730#issuecomment-3549635876"},{"type":"FIX","url":"https://github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879"},{"type":"FIX","url":"https://github.com/nodeca/js-yaml/commit/5278870a17454fe8621dbd8c445c412529525266"}],"database_specific":{"cna_assigner":"GitHub_M","cwe_ids":["CWE-1321"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/64xxx/CVE-2025-64718.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"}]}