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.6% (45th percentile of EPSS-scored CVEs). 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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.
githubMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17900139052026-09-30redhat
redhatansible-automation-platform/automation-portal:17902549632026-09-28redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat
redhatrhtas/rekor-search-ui-rhel9:17897258182026-09-23redhat
redhatautomation-platform-ui-0:2.6.14-1.el9ap2026-09-23redhat
redhatautomation-gateway-0:2.5.20260923-1.el9ap2026-09-23redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595732026-09-17redhat
redhatopenshift4/ose-console-rhel9:17888059262026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896155932026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896150952026-09-17redhat
redhatrhem/flightctl-ui-rhel9:17894867502026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894861812026-09-16redhat
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-142026-09-16redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-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
redhatopenshift4/nmstate-console-plugin-rhel9:17876312212026-09-03redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatopenshift-gitops-1/argocd-rhel9:17877303762026-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

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, 4.2.0+~4.0.9-1
  • every version up to 4.2.0+~4.0.9-2: fixed in 4.2.0+~4.0.9-2
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
js-yaml—
  • 3.0.0 up to 3.15.0: fixed in 3.15.0
  • 4.0.0 up to 4.3.0: fixed in 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 7× in last 7d / 41× 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 218 total refreshes for this CVE.

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

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

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 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 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59869?
CVE-2026-59869 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59869?
A fix for CVE-2026-59869 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59869 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-59869

Explore →

Is Your Infrastructure Affected by CVE-2026-59869?

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

Book a Demo →Browse All CVEs