cve.bz

CVE-2026-59323 spring micrometer tracing

5.3 mediumEPSS 0.4%

Medium (5.3) in spring micrometer tracing. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
An application using Micrometer Tracing with W3C baggage propagation in the Brave bridge is vulnerable to denial of service (DoS) due to unbounded object allocation when extracting incoming baggage headers. Micrometer Tracing 1.7.0 Micrometer Tracing 1.6.0 - 1.6.6 Micrometer Tracing 1.5.0 - 1.5.12 Micrometer Tracing 1.4.13 and earlier

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-59323 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59323?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59323?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59323 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • spring:micrometer tracing

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Micrometer Tracing1.7.0
Spring Micrometer Tracingfrom 1.6.0 through 1.6.6
Spring Micrometer Tracingfrom 1.5.0 through 1.5.12
Spring Micrometer Tracingthrough 1.4.13

Red Hat

Red Hat rates this Important.

Red Hat's statement

A denial of service vulnerability was found in Micrometer Tracing's Brave bridge when using W3C baggage propagation. An unauthenticated remote attacker can send HTTP requests with excessively large `baggage` headers containing many key-value pairs, triggering unbounded memory allocation and garbage collection pressure. This can lead to high CPU usage and application crashes via OutOfMemoryError, resulting in a denial of service. This vulnerability affects applications using Spring Boot 3.x or later where W3C and baggage propagation are enabled by default, and where the application processes requests from untrusted sources. The impact depends on whether network components adequately limit HTTP header sizes.

Red Hat's mitigation

Update io.micrometer:micrometer-tracing-bridge-brave to version 1.6.7 or later. As a workaround, configure network components (HTTP servers, proxies, load balancers) to enforce strict limits on HTTP header sizes, particularly for the `baggage` header. Applications can also disable baggage propagation if this feature is not required, or implement application-level validation to reject requests with excessively large baggage headers.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spaces 3.31devspaces/openvsx-rhel9:1792494821Fixed 2026-10-26RHSA-2026:90321
Red Hat OpenShift Dev Spaces 3.31devspaces/pluginregistry-rhel9:1792495212Fixed 2026-10-26RHSA-2026:90321

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59323.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON