npm
CVE-2026-84375
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
- Severity
- High 7.5
- Published
- 8 Sept 2026
- Last changed
- 8 Sept 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 3.15.2, 4.3.2
- Exploit chance
- 0.5% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Also known as
- GHSA-2883-xcg3-v3hh
- Sources
- OSV.dev and GitHub
Description
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.
An attacker can submit a relatively small YAML document that causes prolonged CPU consumption despite the default maxTotalMergeKeys limit.
In v3 & v4, merge is enabled by default. So, the severity score is higher.
Affected software
| Software | Affected versions |
|---|---|
js-yamlnpm · osv:npm:js-yaml |
|
About js-yaml
- Weekly downloads (npm)
- 399,660,092npm, 17 Nov 2026
Vulnerabilities in js-yaml
- In our list
- 4
- Published in the last 12 months
- 4
- Critical, last 12 months
- 0
- High, last 12 months
- 3
- Known exploited
- 0
- GHSA-5p4m-2wfm-xmqjJS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backportedHigh 7.5 6 Aug 2026
- CVE-2026-59869js-yaml: YAML merge-key chains can force quadratic CPU consumptionHigh 7.5 20 Jul 2026
- CVE-2026-53550JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliasesMedium 5.3 15 Jun 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-84375
- GitHub Advisory Database https://github.com/advisories/GHSA-2883-xcg3-v3hh