Summary
js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources
Impact
When merge keys are enabled, an attacker can submit a relatively small YAML document that causes prolonged CPU consumption despite the default maxTotalMergeKeys limit.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
GHSA-R3PH-W7GJ-G6XM has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.4.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Count every merge source mapping as one budget unit in addition to counting its keys.
Frequently Asked Questions
- What is GHSA-R3PH-W7GJ-G6XM? GHSA-R3PH-W7GJ-G6XM is a medium-severity uncontrolled resource consumption vulnerability in js-yaml (npm), affecting versions >= 5.0.0, <= 5.4.0. It is fixed in 5.4.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is GHSA-R3PH-W7GJ-G6XM? GHSA-R3PH-W7GJ-G6XM has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of js-yaml are affected by GHSA-R3PH-W7GJ-G6XM? js-yaml (npm) versions >= 5.0.0, <= 5.4.0 is affected.
- Is there a fix for GHSA-R3PH-W7GJ-G6XM? Yes. GHSA-R3PH-W7GJ-G6XM is fixed in 5.4.1. Upgrade to this version or later.
- Is GHSA-R3PH-W7GJ-G6XM exploitable, and should I be worried? Whether GHSA-R3PH-W7GJ-G6XM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-R3PH-W7GJ-G6XM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-R3PH-W7GJ-G6XM? Upgrade
js-yamlto 5.4.1 or later.