Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE
| Date | Total | Labels |
|---|
| 2026-09-03 | 1 | General1 |
| 2026-09-09 | 1 | Disclosure1 |
🔴 js-yaml, Denial of Service (Resource Exhaustion), #CVE-2026-84375 (High) -DC-Sep2026-2272 https://dailycve.com/js-yaml-denial-of-service-resource-exhaustion-cve-2026-84375-high-dc-sep2026-2272/
Post summary
A new CVE-2026-84375 affecting js-yaml has been disclosed, describing a resource exhaustion denial of service vulnerability with high severity.
CVE-2026-84375 js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2 and 4.3.2, maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty m… https://www.cve.org/CVERecord?id=CVE-2026-84375
Post summary
The entry references CVE-2026-84375 in js-yaml, detailing a merge-key counting issue across certain versions, but offers no PoC, exploit, active exploitation data, or patch information.