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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-400",
"CWE-407"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/84xxx/CVE-2026-84375.json"
}{
"extracted_events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.15.2"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.3.2"
},
{
"introduced": "5.0.0"
},
{
"fixed": "5.4.1"
}
],
"source": [
"AFFECTED_FIELD",
"REFERENCES"
]
}