PoC Monitor
← All CVEs
CVE-2026-84375published 1 Sep 2026 21:43 UTCData: JSON · API

Nodeca js-yaml

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in applications that parse untrusted YAML, and merge processing is enabled by default on these release lines. In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions 3.15.2, 4.3.2, and 5.4.1.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-400
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

nodeca js-yaml
  • >= 3.0.0, < 3.15.2
  • >= 4.0.0, < 4.3.2
  • >= 5.0.0, < 5.4.1

Fixed in 3.15.2, 4.3.2, 5.4.1

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published1 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.