CVE-2026-59869

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% 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
Trending — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in versions 3.15.0 and 4.3.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

YAML merge-key chains can force quadratic CPU consumption in js-yaml · Advisory · nodeca/js-yaml · GitHub

https://github.com/nodeca/js-yaml/security/advisories/GHSA-52cp-r559-cp3m
github_commit

commit 59423c6f8cdc (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 59423c6f8cdc — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/59423c6f8cdc78742ac00e25a4dd39ef16b702e4
github_commit

commit 24f13e79ee13 (nodeca/js-yaml)

Fix landed in nodeca/js-yaml commit 24f13e79ee13 — awaiting tagged release

https://github.com/nodeca/js-yaml/commit/24f13e79ee1343a7e30bd6f6c9d9cdbf0ac9b2b7

Vendor Advisories for CVE-2026-59869(20)

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

Patch Availability(29)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-142026-09-16redhat
redhatjs-yaml2026-09-10redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatopenshift-gitops-1/argocd-rhel9:17877303762026-09-03redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17876312212026-09-03redhat
redhatopenshift4/ose-console-rhel9:17875504842026-09-02redhat
redhatdevspaces/openvsx-rhel9:17877591452026-09-01redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17875903902026-09-01redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17877363962026-09-01redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17872506172026-08-27redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17871661902026-08-25redhat
redhatopenshift4/ose-console-rhel9:17870808922026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatrhtas/rekor-search-ui-rhel9:17873055492026-08-25redhat
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatmulticluster-engine/console-mce-rhel9:17869119772026-08-19redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17865146202026-08-19redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17865327102026-08-19redhat
redhatrhacm2/console-rhel9:17869083612026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17866295482026-08-19redhat
redhatodf4/rook-ceph-rhel9-operator:17867031432026-08-18redhat
redhatopenshift4/nmstate-console-plugin-rhel9:17866063072026-08-18redhat

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 rangeFixed inDependents
node-js-yaml3.14.1+dfsg+~3.12.6-2 ... 4.2.0+~4.0.9-1 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
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——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
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——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-js-yaml4.1.0+dfsg+~4.0.5-7, 4.1.1+dfsg+~4.0.9-1, 4.2.0+~4.0.9-14.2.0+~4.0.9-2—
npm(1)
PackageVulnerable rangeFixed inDependents
js-yaml—4.3.0—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 62× 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 193 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-59869?
CVE-2026-59869 is a high vulnerability published on July 8, 2026. js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of mappings uses merge keys where each mapping merges the previous one. This issue is fixed in…
When was CVE-2026-59869 disclosed?
CVE-2026-59869 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59869 actively exploited?
CVE-2026-59869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all scored CVEs.
What is the CVSS score of CVE-2026-59869?
CVE-2026-59869 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59869, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59869?

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

Start Free Scan →Browse All CVEs