All vulnerabilities

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
Weakness
Uncontrolled resource consumption (CWE-400)Inefficient algorithmic complexity (CWE-407)
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.

From the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
js-yamlnpm · osv:npm:js-yaml
  • From 3.0.0 before 3.15.2
  • From 4.0.0 before 4.3.2

About js-yaml

Weekly downloads (npm)
399,660,092npm, 17 Nov 2026

References