CVE-2026-53550

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

June 15, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Quadratic-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-rp68

Vendor Advisories for CVE-2026-53550(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17872506172026-08-27redhat
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatnodejs22-main-22.23.1-2.1.hum12026-07-12redhat
redhatnodejs24-main-24.18.0-0.3.hum12026-07-11redhat
redhatnodejs25-main-25.9.0-1.3.hum12026-07-10redhat
redhatdotnet8-0-main-8.0.128-1.1.hum12026-07-10redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml3.14.1+dfsg+~3.12.6-2 ... 4.2.0+~4.0.9-1 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-1, 4.2.0+~4.0.9-2, 4.3.2+~4.0.9-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-1, 4.2.0+~4.0.9-2, 4.3.2+~4.0.9-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1
  • every version up to 4.2.0+~4.0.9-1: fixed in 4.2.0+~4.0.9-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
js-yaml—
  • 4.0.0 up to 4.2.0: fixed in 4.2.0
  • every version up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× 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.

Showing the most recent 100 of 172 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-03 07:39 UTCOSV refresh
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 15:03 UTCEPSS rescore
  7. 2026-09-29 15:22 UTCEPSS rescore
  8. 2026-09-28 13:51 UTCEPSS rescore
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-14 03:46 UTCEG score recompute
  18. 2026-09-14 03:46 UTCVendor advisory
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-08-30 22:59 UTCEG score recompute
  5. 2026-08-30 22:59 UTCVendor advisory
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 23:34 UTCEG score recompute
  13. 2026-08-24 23:34 UTCVendor advisory
  14. 2026-08-23 09:48 UTCEG score recompute
  15. 2026-08-23 09:48 UTCVendor advisory
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 18:57 UTCEG score recompute
  19. 2026-08-21 18:57 UTCVendor advisory
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 16:21 UTCEG score recompute
  22. 2026-08-20 16:21 UTCVendor advisory
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 13:15 UTCEG score recompute
  25. 2026-08-19 13:15 UTCVendor advisory
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 13:47 UTCEPSS rescore
  28. 2026-08-16 16:26 UTCEG score recompute
  29. 2026-08-16 16:26 UTCVendor advisory
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 14:22 UTCEG score recompute
  33. 2026-08-15 14:22 UTCVendor advisory
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 12:17 UTCEG score recompute
  36. 2026-08-14 12:17 UTCVendor advisory
  37. 2026-08-13 22:00 UTCEPSS rescore
  38. 2026-08-13 10:13 UTCEG score recompute
  39. 2026-08-13 10:13 UTCVendor advisory
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 08:08 UTCEG score recompute
  42. 2026-08-12 08:08 UTCVendor advisory
  43. 2026-08-11 06:04 UTCEG score recompute
  44. 2026-08-11 06:04 UTCVendor advisory
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 03:59 UTCEG score recompute
  47. 2026-08-10 03:59 UTCVendor advisory
  48. 2026-08-09 13:46 UTCEPSS rescore
  49. 2026-08-09 01:55 UTCEG score recompute
  50. 2026-08-09 01:55 UTCVendor advisory
  51. 2026-08-08 16:37 UTCEPSS rescore
  52. 2026-08-07 23:51 UTCEG score recompute
  53. 2026-08-07 23:51 UTCVendor advisory
  54. 2026-08-06 21:48 UTCEG score recompute
  55. 2026-08-06 21:48 UTCVendor advisory
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-05 19:43 UTCEG score recompute
  58. 2026-08-05 19:43 UTCVendor advisory
  59. 2026-08-05 19:17 UTCEPSS rescore
  60. 2026-08-04 16:51 UTCEG score recompute
  61. 2026-08-04 16:51 UTCVendor advisory
  62. 2026-08-04 15:10 UTCEPSS rescore
  63. 2026-08-04 10:39 UTCEPSS rescore
  64. 2026-08-03 14:44 UTCEG score recompute
  65. 2026-08-03 14:44 UTCVendor advisory
  66. 2026-08-03 10:36 UTCEPSS rescore
  67. 2026-08-02 12:22 UTCEG score recompute
  68. 2026-08-02 12:22 UTCVendor advisory
  69. 2026-08-02 02:27 UTCEPSS rescore
  70. 2026-08-01 10:14 UTCEG score recompute
  71. 2026-08-01 10:14 UTCVendor advisory
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-31 08:10 UTCEG score recompute
  74. 2026-07-31 08:10 UTCVendor advisory
  75. 2026-07-30 16:28 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53550?
CVE-2026-53550 is a medium vulnerability published on June 15, 2026. 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…
When was CVE-2026-53550 disclosed?
CVE-2026-53550 was first published on June 15, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53550 actively exploited?
CVE-2026-53550 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53550?
CVE-2026-53550 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53550?
A fix for CVE-2026-53550 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53550 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53550

Explore →

Is Your Infrastructure Affected by CVE-2026-53550?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs