CVE-2026-59295: CWE-401: Missing Release of Memory after Effective Lifetime in VMware (Broadcom) io.micrometer:micrometer-core
Micrometer-instrumented Apache HttpAsyncClient (4.x or 5.x) usage via MicrometerHttpClientInterceptor can leak memory unboundedly when asynchronous requests fail before receiving a response (e.g. connection resets or timeouts). Tracking state for these requests remains in memory indefinitely, and sustained failures lead to heap exhaustion and OutOfMemoryError crashes.
AI Analysis
Technical Summary
CVE-2026-59295 describes a memory leak (CWE-401) in VMware (Broadcom) io.micrometer:micrometer-core versions 1.14.0, 1.15.0, 1.16.0, and 1.17.0. The vulnerability occurs when Micrometer-instrumented Apache HttpAsyncClient (4.x or 5.x) asynchronous requests fail before a response is received. The MicrometerHttpClientInterceptor fails to release tracking state memory for these failed requests, causing indefinite retention of this state. Sustained failures can exhaust heap memory, resulting in OutOfMemoryError crashes. The CVSS 3.1 base score is 5.9 (medium severity), reflecting network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, but high availability impact. No patch or remediation guidance is currently available.
Potential Impact
The vulnerability can cause unbounded memory consumption in applications using the affected Micrometer versions with Apache HttpAsyncClient instrumentation. This can lead to heap exhaustion and application crashes due to OutOfMemoryError, impacting availability. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should monitor application memory usage and consider mitigating asynchronous request failures to reduce memory leak risk. No official fix or temporary workaround is currently documented.
CVE-2026-59295: CWE-401: Missing Release of Memory after Effective Lifetime in VMware (Broadcom) io.micrometer:micrometer-core
Description
Micrometer-instrumented Apache HttpAsyncClient (4.x or 5.x) usage via MicrometerHttpClientInterceptor can leak memory unboundedly when asynchronous requests fail before receiving a response (e.g. connection resets or timeouts). Tracking state for these requests remains in memory indefinitely, and sustained failures lead to heap exhaustion and OutOfMemoryError crashes.
CVSS v3.1
Score 5.9medium
Affected software
pkg:maven/io.micrometer/micrometer-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-59295 describes a memory leak (CWE-401) in VMware (Broadcom) io.micrometer:micrometer-core versions 1.14.0, 1.15.0, 1.16.0, and 1.17.0. The vulnerability occurs when Micrometer-instrumented Apache HttpAsyncClient (4.x or 5.x) asynchronous requests fail before a response is received. The MicrometerHttpClientInterceptor fails to release tracking state memory for these failed requests, causing indefinite retention of this state. Sustained failures can exhaust heap memory, resulting in OutOfMemoryError crashes. The CVSS 3.1 base score is 5.9 (medium severity), reflecting network attack vector, high attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, but high availability impact. No patch or remediation guidance is currently available.
Potential Impact
The vulnerability can cause unbounded memory consumption in applications using the affected Micrometer versions with Apache HttpAsyncClient instrumentation. This can lead to heap exhaustion and application crashes due to OutOfMemoryError, impacting availability. There is no impact on confidentiality or integrity. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should monitor application memory usage and consider mitigating asynchronous request failures to reduce memory leak risk. No official fix or temporary workaround is currently documented.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-07-04T18:13:34.323Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a8c1b7dacd9273b495ef863
Added to database: 08/24/2026, 10:22:53 UTC
Last enriched: 08/24/2026, 10:37:06 UTC
Last updated: 08/24/2026, 11:16:49 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.