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

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0054, the 46th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 8 Sept 2026. New records show when each source confirmed them.

Sources

• GitHub Advisory Database: GHSA-2883-xcg3-v3hh
• OSV: GHSA-2883-xcg3-v3hh
• github.com/nodeca/js-yaml/security/advisories/GHSA-2883-xcg3-v3hh
• nvd.nist.gov/vuln/detail/CVE-2026-84375
• github.com/nodeca/js-yaml/pull/797
• github.com/nodeca/js-yaml/commit/3485bc06ff8a0251505f44a00414d90df2466639
• github.com/nodeca/js-yaml/commit/6a8e05f9a485188ed730ac81e81ae221352ef480
• github.com/nodeca/js-yaml/commit/d90b6612a5a84385bdcb556c44578eac76dc0f6b
• github.com/nodeca/js-yaml
• github.com/nodeca/js-yaml/releases/tag/3.15.2
• github.com/nodeca/js-yaml/releases/tag/4.3.2

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.