GHSA-mh29-5h37-fv8m

js-yaml has prototype pollution in merge (<<)

At a glance

Published
Updated
CVE
CVE-2025-64718
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Description

### 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

Affected packages

PackageVersions
npm · js-yamlintroduced 4.0.0, fixed 4.1.1
npm · js-yamlintroduced 0, fixed 3.14.2

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database