CVE-2026-73643: js-yaml: Exponential parsing time in flow collections leads to denial of service
Summary Parsing a small YAML document can take exponential time. An application that calls load() or loadAll() on untrusted input can be hung by a payload under 200 bytes. Details When an entry in a flow sequence turns out to be a key: value pair, the parser rewinds and parses that entry a second time as the key.
Published Jul 24, 2026 · Updated Aug 13, 2026
Affected packages
js-yaml
- Ecosystem
- npm
- Affected
- >= 5.0.0, <= 5.2.1
- Fixed in
- 5.2.2
- Check
npm ls js-yaml
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Parsing a small YAML document can take exponential time. An application that calls load() or loadAll() on untrusted input can be hung by a payload under 200 bytes.
Details
When an entry in a flow sequence turns out to be a key: value pair, the parser rewinds and parses that entry a second time as the key. If the key is itself a nested flow sequence of the same shape, every level is parsed twice, so the total work is O(2^n) in the nesting depth. The default maxDepth of 100 does not help, because the time is already unmanageable at about 30 to 40 levels.
Root cause, potentially the: readFlowCollection in parser.ts, the restoreState followed by a second parseNode further down.
PoC
const yaml = require('js-yaml')
const n = 30
yaml.load('[ '.repeat(n) + '1' + ' ]: 0'.repeat(n))With default options: 22 levels takes about 1 second, 26 levels about 17 seconds, 30 levels over 2 minutes. The input stays under 200 bytes and grows linearly with n.
Impact
Denial of service. A single small request can keep one CPU busy for minutes or longer and blocks the Node event loop, so one request can stall the whole process. No anchors, aliases, merges, tags, or non default options are required, and it reproduces on the default schema.
Credited to lissy93.
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 entriesGHSA-r3ph-w7gj-g6xm
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
medium5.3Sep 29, 2026CVE-2026-84375
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
high7.5Sep 8, 2026GHSA-5p4m-2wfm-xmqj
JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
high7.5Aug 6, 2026CVE-2026-59868
js-yaml: YAML merge-key chains can force quadratic CPU consumption in js-yaml
medium5.3Jul 20, 2026CVE-2026-59869
js-yaml: YAML merge-key chains can force quadratic CPU consumption
high7.5Jul 20, 2026CVE-2026-59870
js-yaml: Quadratic-complexity (O(n^2)) DoS via !!omap tag in YAML11_SCHEMA
medium5.3Jul 20, 2026
