CVE-2026-59323: Spring Micrometer Tracing · Unthrottled Resource Allocation
Affects Spring Micrometer TracingSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringMicrometer Tracing | Affected
| Fixed in– |
AI-suggested
Until a fix is available, consider limiting or validating incoming baggage headers to prevent unbounded resource allocation.
Description
CVE-2026-59323 is a medium severity vulnerability in Spring Micrometer Tracing that allows denial of service (DoS) due to unbounded resource allocation when processing incoming baggage headers with W3C baggage propagation in the Brave bridge. This affects multiple versions including 1.7.0, 1.6.0 through 1.6.6, 1.5.0 through 1.5.12, and versions up to 1.4.13. The flaw is related to allocation of resources without limits or throttling, potentially causing service disruption.