js-yaml is a JavaScript YAML parser and dumper. Prior to 4.2.0 and 3.15.0, a crafted YAML document can trigger algorithmic CPU exhaustion in js-yaml merge-key processing (<<) by repeating the same alias many times in a merge sequence. This causes quadratic parse-time behavior relative to input size and can block a Node.js worker/event loop for seconds with a relatively small payload (tens of KB), resulting in denial of service. The issue is in merge handling inside lib/loader.js. This vulnerability is fixed in 4.2.0 and 3.15.0.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-h67p-54hq-rp68 Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · nodecaNVD modified 2026-10-25 23:10
Affected (CPE criteria) 1
cpe:2.3:a:nodeca:js-yaml:*:*:*:*:*:node.js:*:*
References 1
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-h67p-54hq-rp68 Exploit, Mitigation, Vendor Advisory