js-yaml is a JavaScript YAML parser and dumper. From 5.0.0 before 5.2.0, when merge keys are enabled, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in version 5.2.0.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/nodeca/js-yaml/commit/3105455b81dee69e0fd36e09ac0b2ccfdb54adc1 Patch
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-g796-fgmg-93mv Exploit, Vendor Advisory
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-g796-fgmg-93mv Exploit, 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 7.5 · nodecaNVD modified 2026-10-25 20:10
Affected (CPE criteria) 1
cpe:2.3:a:nodeca:js-yaml:*:*:*:*:*:node.js:*:*
References 4
- https://github.com/nodeca/js-yaml/commit/3105455b81dee69e0fd36e09ac0b2ccfdb54adc1 Patch
- https://github.com/nodeca/js-yaml/releases/tag/5.2.0 Release Notes
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-g796-fgmg-93mv Exploit, Vendor Advisory
- https://github.com/nodeca/js-yaml/security/advisories/GHSA-g796-fgmg-93mv Exploit, Vendor Advisory