CVE-2026-84375

published 1 Sep 2026 · updated 28 Sep 2026

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

7.5HighCVSS 7.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nodeca>=3.0.0 <3.15.2, >=4.0.0 <4.3.2, >=5.0.0 <5.4.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-84375 severity on Zeptric[![CVE-2026-84375](https://zeptric.io/badge/cve/CVE-2026-84375.svg)](https://zeptric.io/cve/CVE-2026-84375)