# CVE-2026-59296: Micrometer StatsD and Logging meter registries line-protocol and log injection vulnerability

> Attackers can inject malicious content into metrics or logs via unnormalized input, potentially corrupting data or misleading monitoring systems.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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:** CLEANSTART-2026-AS15122, CLEANSTART-2026-DL27432, CLEANSTART-2026-GB94492, CLEANSTART-2026-OZ28638, CLEANSTART-2026-RM52216, GHSA-8jcv-3c3x-vwg4

## What is CVE-2026-59296?

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

### Official description

Using untrusted, non-normalized input as-is for metrics data (such as metric names, tag keys, or tag values) is a dangerous antipattern that general-purpose instrumentation should never perform.
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

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

Upgrade to a fixed version.

## Is CVE-2026-59296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59296 is a medium-severity vulnerability in Spring Micrometer, 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-59296 in the wild and no public exploit code.

Affected product: Spring Micrometer. 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-59296/ (Markdown: https://insights.sbomify.com/CVE-2026-59296/index.md)
```

## Sources

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

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