CVE-2026-59301

MEDIUMNVD 4.94.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.9 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0

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

Potential for logging sensitive data in Spring Cloud Function Azure. 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
4.9
EG Score
4.9(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

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
Severity49% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 4, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

Potential for logging sensitive data in Spring Cloud Function Azure

https://spring.io/security/cve-2026-59301

Vendor Advisories for CVE-2026-59301(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 19× in last 7d / 63× 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.

  1. 2026-09-20 15:40 UTCEG score recompute
  2. 2026-09-20 15:40 UTCGHSA enrichment
  3. 2026-09-19 14:19 UTCEG score recompute
  4. 2026-09-19 14:19 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 12:59 UTCEG score recompute
  7. 2026-09-18 12:59 UTCGHSA enrichment
  8. 2026-09-17 19:31 UTCEPSS rescore
  9. 2026-09-17 11:39 UTCEG score recompute
  10. 2026-09-17 11:39 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 10:16 UTCEG score recompute
  13. 2026-09-16 10:16 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 08:55 UTCEG score recompute
  16. 2026-09-15 08:55 UTCGHSA enrichment
  17. 2026-09-15 03:11 UTCEPSS rescore
  18. 2026-09-14 07:34 UTCEG score recompute
  19. 2026-09-14 07:34 UTCGHSA enrichment
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-13 06:14 UTCEG score recompute
  22. 2026-09-13 06:14 UTCGHSA enrichment
  23. 2026-09-12 04:54 UTCEG score recompute
  24. 2026-09-12 04:54 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 38 more
  1. 2026-09-11 03:33 UTCEG score recompute
  2. 2026-09-11 03:33 UTCGHSA enrichment
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-10 02:12 UTCGHSA enrichment
  5. 2026-09-09 00:51 UTCEG score recompute
  6. 2026-09-09 00:51 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 23:31 UTCEG score recompute
  9. 2026-09-07 23:31 UTCGHSA enrichment
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 22:11 UTCEG score recompute
  12. 2026-09-06 22:11 UTCGHSA enrichment
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-05 20:50 UTCEG score recompute
  15. 2026-09-05 20:50 UTCGHSA enrichment
  16. 2026-09-04 19:30 UTCEG score recompute▲ 1.80
  17. 2026-09-04 19:30 UTCGHSA enrichment
  18. 2026-09-04 19:28 UTCNVD updateCVSS v3 → 4.9 · severity → MEDIUM
  19. 2026-09-04 09:15 UTCEG score recompute
  20. 2026-09-04 09:15 UTCGHSA enrichment
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:22 UTCEG score recompute
  26. 2026-09-01 04:21 UTCGHSA enrichment
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 01:22 UTCEPSS rescore
  29. 2026-08-28 23:28 UTCEG score recompute
  30. 2026-08-28 23:28 UTCGHSA enrichment
  31. 2026-08-28 23:03 UTCEG score recompute
  32. 2026-08-28 23:03 UTCGHSA enrichment
  33. 2026-08-28 21:42 UTCEPSS rescore
  34. 2026-08-28 19:00 UTCEG score recompute
  35. 2026-08-28 19:00 UTCGHSA enrichment
  36. 2026-08-27 20:26 UTCEG score recompute
  37. 2026-08-27 20:16 UTCEG score recompute
  38. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2026-59301?
CVE-2026-59301 is a medium vulnerability published on August 27, 2026. Potential for logging sensitive data in Spring Cloud Function Azure. 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 CVE-2026-59301 disclosed?
CVE-2026-59301 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59301 actively exploited?
CVE-2026-59301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.7% of all scored CVEs.
What is the CVSS score of CVE-2026-59301?
CVE-2026-59301 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-59301?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59301, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59301?

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

Start Free Scan →Browse All CVEs