# CVE-2026-59323: Micrometer Tracing Brave Bridge W3C Baggage propagation DoS vulnerability

> Attackers can cause denial of service via unbounded memory allocation in Micrometer Tracing when W3C baggage propagation is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** CLSA-2026-1792395367, CLSA-2026-1792395420, GHSA-rj39-56xf-v987

## What is CVE-2026-59323?

CVE-2026-59323 is a medium-severity denial of service vulnerability in Spring Micrometer Tracing, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-59323?


## How do I fix CVE-2026-59323?

Upgrade to a fixed version.

## Is CVE-2026-59323 being exploited?

There is no known exploitation of CVE-2026-59323 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59323 and fix it if it is affected.

What it is: CVE-2026-59323 is a medium-severity denial of service vulnerability in Spring Micrometer Tracing, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59323 in the wild and no public exploit code.

Affected product: Spring Micrometer Tracing. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59323/ (Markdown: https://insights.sbomify.com/CVE-2026-59323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59323
- OSV: https://osv.dev/vulnerability/CVE-2026-59323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59323/
Summaries are generated and may contain mistakes; the official description above is the record.