CVE-2026-59869

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-20. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-42301 (ENISA EUVD) · GHSA-52cp-r559-cp3m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

October 25, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-console:17918364682026-10-22redhat
redhatrhoai/odh-mod-arch-eval-hub-rhel9:17918612142026-10-19redhat
redhatopenshift4/ose-console:17912992432026-10-15redhat
redhatopenshift4/ose-console:17912453422026-10-15redhat
redhatopenshift4/ose-console:17906060512026-10-08redhat
redhatopenshift4/ose-console-rhel9:17906361712026-10-08redhat
redhatopenshift4/ose-console-rhel9:17899395652026-10-01redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17900139052026-09-30redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat
redhatansible-automation-platform/automation-portal:17902549632026-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-remediations-rhel9:17896155932026-09-17redhat
redhatsatellite/iop-remediations-rhel9:17896150952026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595652026-09-17redhat
redhatsatellite/iop-advisor-frontend-rhel9:17896595732026-09-17redhat
redhatrhmtc/openshift-migration-ui-rhel8:17895463732026-09-17redhat
redhatopenshift4/ose-console-rhel9:17888059262026-09-17redhat
redhatrhem/flightctl-ui-rhel10:17894861812026-09-16redhat
redhatrhem/flightctl-ui-ocp-rhel9:17894864462026-09-16redhat
redhatrhem/flightctl-ui-rhel9:17894867502026-09-16redhat
redhatrhem/flightctl-ui-rhel10:17894881112026-09-16redhat
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
npmjs-yaml @ 4.3.0 (fixes >= 4.0.0, < 4.3.0)—ghsa
npmjs-yaml @ 3.15.0 (fixes >= 3.0.0, < 3.15.0)—ghsa

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(2)

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 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 257 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59869?
CVE-2026-59869 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-59869 published?
The CVE record for CVE-2026-59869 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
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 (47th 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.