CVE-2026-59675

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (SUSE) lists SUSE Rancher versions 2.14.0 up to but not including 2.14.4, 2.13.0 up to but not including 2.13.8 and 2.12.0 up to but not including 2.12.12 as affected. No release containing a fix is confirmed on record.

When API audit logging is enabled, the middleware reads the entire HTTP request body into memory without enforcing a size limit on login endpoints. Because the audit middleware is positioned earlier in the handler chain than Rancher's APIBodyLimitingHandler, the body-size cap (default 1 MiB) is bypassed for requests that pass through the audit copyReqBody path. An unauthenticated attacker can send arbitrarily large request bodies to the public login endpoints, causing the Rancher Manager server process to allocate memory proportional to the supplied body size. With just a few concurrent connections, this can exhaust available memory and terminate the Rancher Manager plane process, making the Rancher API and UI unavailable and interrupting management of all downstream clusters.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation none (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.

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

August 5, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Rancher Audit-Log Middleware Unauthenticated Memory Exhaustion Denial of Service · Advisory · rancher/rancher · GitHub

https://github.com/rancher/rancher/security/advisories/GHSA-g4f6-44g4-23xm
Web page

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-59675

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 51× 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 125 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 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59675?
CVE-2026-59675 is a high-severity vulnerability; its CVE record was published on August 5, 2026. When API audit logging is enabled, the middleware reads the entire HTTP request body into memory without enforcing a size limit on login endpoints. Because the audit middleware is positioned earlier in the handler chain than Rancher's APIBodyLimitingHandler, the body-size cap (default 1 MiB) is…
When was the CVE record for CVE-2026-59675 published?
The CVE record for CVE-2026-59675 was published on August 5, 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 September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-59675 actively exploited?
CVE-2026-59675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59675?
CVE-2026-59675 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-59675?
No fix for CVE-2026-59675 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (SUSE) lists SUSE Rancher versions 2.14.0 up to but not including 2.14.4, 2.13.0 up to but not including 2.13.8 and 2.12.0 up to but not including 2.12.12 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59675

Explore →

Is Your Infrastructure Affected by CVE-2026-59675?

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

Book a Demo →Browse All CVEs