CVE-2025-64718
Nodeca Js-yaml vulnerability
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 products
Js-yaml. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Nodeca Js-yaml runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/nodeca/js-yaml/security/advisories/GHSA-mh29-5h37-fv8m · Vendor Advisory
- github.com/advisories/GHSA-mh29-5h37-fv8m · Vendor Advisory
- github.com/nodeca/js-yaml/commit/383665ff4248ec2192d1274e934462bb30426879 · Patch
- github.com/nodeca/js-yaml/commit/5278870a17454fe8621dbd8c445c412529525266 · Patch
- github.com/nodeca/js-yaml/issues/730#issuecomment-3549635876
- nvd.nist.gov/vuln/detail/CVE-2025-64718
- nvd.nist.gov/vuln/detail/CVE-2025-64718
- cve.org/CVERecord?id=CVE-2025-64718
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.