It is possible for outbound HTTP requests using a Micrometer-instrumented client to cause a denial-of-service (DoS) condition due to an unbounded memory leak. Micrometer 1.17.0 Micrometer 1.16.0 - 1.16.6 Micrometer 1.15.0 - 1.15.12 Micrometer 1.14.0 - 1.14.16 Micrometer 1.9.18 and earlier
CVE-2026-59295
Score 5.9 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 24, 2026Micrometer instrumentation of Apache HttpAsyncClient DoS vulnerability
https://spring.io/security/cve-2026-59295Vendor Advisories for CVE-2026-59295(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 25× in last 7d / 25× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:17 UTCEG score recompute
- 2026-08-29 19:16 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:09 UTCEG score recompute
- 2026-08-28 19:09 UTCGHSA enrichment
- 2026-08-27 20:20 UTCEG score recompute
- 2026-08-27 20:20 UTCGHSA enrichment
- 2026-08-27 15:33 UTCEG score recompute
- 2026-08-27 15:32 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 15:28 UTCEG score recompute
- 2026-08-26 15:28 UTCGHSA enrichment
- 2026-08-26 15:27 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 15:25 UTCEG score recompute
- 2026-08-25 15:25 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 15:23 UTCEG score recompute
- 2026-08-24 15:23 UTCGHSA enrichment
- 2026-08-24 14:37 UTCEG score recompute
- 2026-08-24 14:37 UTCGHSA enrichment
- 2026-08-24 11:23 UTCEG score recompute
- 2026-08-24 10:22 UTCEG score recompute
- 2026-08-24 10:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-401
- CVE-2018-0158NVD 8.6EG 9.0 KEVEPSS p94CRITICAL
- CVE-2019-17340EG 8.8HIGH
- CVE-2019-1708EG 8.6HIGH
- CVE-2018-15377EG 8.6HIGH
- CVE-2016-6304NVD 7.5EG 8.4EPSS p99HIGH
- CVE-2019-10547EG 7.8HIGH
- CVE-2007-2274EG 7.8EPSS p95HIGH
- CVE-2015-8567EG 7.7EPSS p92HIGH
- CVE-2016-4232NVD 7.5EG 7.7EPSS p98HIGH
- CVE-2018-17240EG 7.5HIGH
Frequently asked(5)
What is CVE-2026-59295?
When was CVE-2026-59295 disclosed?
Is CVE-2026-59295 actively exploited?
What is the CVSS score of CVE-2026-59295?
How do I remediate CVE-2026-59295?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59295
Is Your Infrastructure Affected by CVE-2026-59295?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.