CVE-2026-59297

LOWNVD 3.53.5
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 3.5 under NVD CVSS v3. EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-27) is not newer than that change (2026-09-02), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-67183 (ENISA EUVD) · GHSA-x389-8jh6-xrxm (GitHub Security Advisories)Source: ENISA EUVD

3.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.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 (VMware by Broadcom) lists Spring Cloud Function versions 5.0.0 up to and including 5.0.3, 4.3.0 up to and including 4.3.4 and 4.2.0 up to and including 4.2.7 as affected. No release containing a fix is confirmed on record.

Implementation of isSecure() call of ServerlessHttpServletRequest does not verify the actual scheme. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7

CVSS v3
3.5
EG Score
3.5LOWmedium confidence
EG Risk
16
EG Risk 16/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)
Severity35% × 45%
Impact severity (EG Severity): CVSS 3.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
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 (3.5): severity, escalated by confirmed exploitation. This CVE's 3.5 is its impact severity (EG Severity), not escalated.

EG Severity
3.5 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 27, 2026

Last Modified

September 2, 2026

References (1)

Vendor Advisories for CVE-2026-59297(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× 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.

  1. 2026-10-27 05:55 UTCOSV refresh
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-25 14:16 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-18 03:27 UTCEG score recompute
  13. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-12 15:52 UTCEG score recompute
  20. 2026-10-11 19:36 UTCEG score recompute
  21. 2026-10-11 16:51 UTCEG score recompute
  22. 2026-10-11 14:14 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 63 more
  1. 2026-10-09 07:40 UTCEG score recompute
  2. 2026-10-09 07:40 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  3. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-06 07:31 UTCEG score recompute
  7. 2026-10-06 07:31 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  8. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-03 04:57 UTCEG score recompute
  12. 2026-10-03 04:57 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-30 04:57 UTCEG score recompute
  17. 2026-09-30 04:57 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  18. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-27 00:41 UTCEG score recompute
  22. 2026-09-27 00:41 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-24 00:41 UTCEG score recompute
  26. 2026-09-24 00:41 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  27. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  28. 2026-09-21 00:40 UTCEG score recompute
  29. 2026-09-21 00:40 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  30. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-18 00:40 UTCEG score recompute
  32. 2026-09-18 00:40 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  33. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  35. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-09-15 00:39 UTCEG score recompute
  38. 2026-09-15 00:39 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  39. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  40. 2026-09-12 00:39 UTCEG score recompute
  41. 2026-09-12 00:39 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  42. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-09-09 00:39 UTCEG score recompute
  45. 2026-09-09 00:39 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  46. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  48. 2026-09-05 17:43 UTCEG score recompute
  49. 2026-09-05 17:43 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  50. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  51. 2026-09-02 17:39 UTCEG score recompute▲ 0.40
  52. 2026-09-02 17:38 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  53. 2026-09-02 17:32 UTCNVD updateCVSS v3 → 3.5
  54. 2026-09-02 14:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-08-31 20:48 UTCEG score recompute
  56. 2026-08-31 20:48 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  57. 2026-08-28 21:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  58. 2026-08-28 20:42 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  59. 2026-08-28 19:00 UTCEG score recompute
  60. 2026-08-28 19:00 UTCGHSA enrichmentGHSA-x389-8jh6-xrxm · GitHub severity LOW · GitHub CVSS 3.1
  61. 2026-08-27 20:26 UTCEG score recompute
  62. 2026-08-27 20:16 UTCEG score recomputeFirst assessed: 3.1 LOW
  63. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59297?
CVE-2026-59297 is a low-severity vulnerability; its CVE record was published on August 27, 2026. Implementation of isSecure() call of ServerlessHttpServletRequest does not verify the actual scheme. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7
When was the CVE record for CVE-2026-59297 published?
The CVE record for CVE-2026-59297 was published on August 27, 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 2, 2026; the record at its source may have been updated since.
Is CVE-2026-59297 actively exploited?
CVE-2026-59297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59297?
CVE-2026-59297 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2026-59297?
No fix for CVE-2026-59297 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists Spring Cloud Function versions 5.0.0 up to and including 5.0.3, 4.3.0 up to and including 4.3.4 and 4.2.0 up to and including 4.2.7 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-59297 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59297?

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

Book a Demo →Browse All CVEs