js-yaml is a JavaScript YAML parser and dumper. Prior to 4.2.0 and 3.15.0, a crafted YAML document can trigger algorithmic CPU exhaustion in js-yaml merge-key processing (<<) by repeating the same alias many times in a merge sequence. This causes quadratic parse-time behavior relative to input size and can block a Node.js worker/event loop for seconds with a relatively small payload (tens of KB), resulting in denial of service. The issue is in merge handling inside lib/loader.js. This vulnerability is fixed in 4.2.0 and 3.15.0.
CVE-2026-53550
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 17.3%
- KEV
- Not listed
Published
June 15, 2026
Last Modified
June 29, 2026
Advisory Details (1)
Auto-updated Jun 22, 2026Quadratic-complexity DoS in merge key handling via repeated aliases · Advisory · nodeca/js-yaml · GitHub
https://github.com/nodeca/js-yaml/security/advisories/GHSA-h67p-54hq-rp68Vendor Advisories for CVE-2026-53550(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs26-main-26.4.0-1.3.hum1 | 2026-06-30 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| js-yaml | — | 4.2.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 43× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:21 UTCEG score recompute
- 2026-07-07 00:21 UTCVendor advisory
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 12:09 UTCEG score recompute
- 2026-07-05 12:09 UTCVendor advisory
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 10:03 UTCEG score recompute
- 2026-07-04 10:03 UTCVendor advisory
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 04:09 UTCEG score recompute
- 2026-07-02 02:00 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:56 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 21:45 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 19:40 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
Show 18 moreShow fewer
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 17:35 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 15:30 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:26 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 11:21 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 09:14 UTCEG score recompute
- 2026-06-22 07:11 UTCEG score recompute
- 2026-06-21 04:42 UTCEG score recompute
- 2026-06-20 02:21 UTCEG score recompute
- 2026-06-19 00:07 UTCEG score recompute
- 2026-06-17 21:56 UTCEG score recompute
- 2026-06-16 19:51 UTCEG score recompute
- 2026-06-15 17:46 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Frequently asked(5)
What is CVE-2026-53550?
When was CVE-2026-53550 disclosed?
Is CVE-2026-53550 actively exploited?
What is the CVSS score of CVE-2026-53550?
How do I remediate CVE-2026-53550?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53550
Is Your Infrastructure Affected by CVE-2026-53550?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.