NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2025-64718: js-yaml has prototype pollution in merge (<<)

mediumCVSS 3.1 5.3GHSA-mh29-5h37-fv8m

Impact In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, 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. Patches Problem is patched in js-yaml 4.1.1 and 3.14.2.

Published Nov 14, 2025 · Updated Jan 31, 2026

Affected packages

js-yaml

Ecosystem
npm
Affected
>= 4.0.0, < 4.1.1
Fixed in
4.1.1
Check
npm ls js-yaml

js-yaml

Ecosystem
npm
Affected
< 3.14.2
Fixed in
3.14.2
Check
npm ls js-yaml

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

In js-yaml 4.1.0, 4.0.0, and 3.14.1 and below, 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.

Patches

Problem is patched in js-yaml 4.1.1 and 3.14.2.

Workarounds

You 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).

References

https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html

Credited to Zephkek, mhassan1, opal-visibuild, alexstrive, jlp-craigmorten, turi4200.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries