CVE-2026-59296
Micrometer StatsD and Logging meter registries line-protocol and log injection vulnerability
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. When such unsafe instrumentation is used, the application becomes vulnerable to injection and spoofing attacks because micrometer-registry-statsd and micrometer-core do not sanitize newline characters (\n, \r) by default prior to this fix. * For the StatsD registry in micrometer-registry-statsd (when using the Datadog or Etsy flavor), because the StatsD protocol is newline-delimited, this allows for line-protocol injection (cross-metric spoofing). * For LoggingMeterRegistry in micrometer-core, because metric output is printed line-by-line to log files, this allows for both metric spoofing (if downstream log-metrics scrapers or parsers ingest the log lines as separate metrics) and general log spoofing. Specifically, an application is vulnerable when all the following are true: * The application uses a vulnerable version of io.micrometer:micrometer-registry-statsd or io.micrometer:micrometer-core. * The application uses the Datadog or Etsy flavor of the StatsD registry, or uses LoggingMeterRegistry. * The application instruments meters using user-controlled, unvalidated input for metric names, tag keys, or tag values. When vulnerable, an attacker can break out of the current metric or log line by injecting line terminators. This allows them to spoof arbitrary metrics (e.g., system load, standard JVM metrics, or other business metrics) across the metrics registry namespace (either directly via StatsD protocol or via downstream log-metric scrapers/parsers), as well as inject arbitrary log entries to spoof general log records.
INFO
Published Date :
Aug. 21, 2026, 11:17 a.m.
Last Modified :
Aug. 21, 2026, 11:17 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-59296
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | dcf2e128-44bd-42ed-91e8-88f912c1401d | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update micrometer-registry-statsd and micrometer-core libraries.
- Sanitize newline characters in metric names and tags.
- Validate all user-controlled input before instrumentation.
- Avoid user input for metric names and tags.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-59296.
| URL | Resource |
|---|---|
| https://spring.io/security/cve-2026-59296 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-59296 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-59296
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-59296 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-59296 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 21, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'VMware', 'product': 'Spring Micrometer', 'versions': [{'status': 'affected', 'version': '1.17.0 - 1.17.0'}, {'status': 'affected', 'version': '1.16.0 - 1.16.6'}, {'status': 'affected', 'version': '1.15.0 - 1.15.12'}, {'status': 'affected', 'version': '1.14.0 - 1.14.16'}, {'status': 'affected', 'version': '1.9.18 and earlier'}, {'status': 'unaffected', 'version': '1.17.0.1', 'versionType': 'enterprise support only'}, {'status': 'unaffected', 'version': '1.17.1', 'versionType': 'oss'}, {'status': 'unaffected', 'version': '1.16.6.1', 'versionType': 'enterprise support only'}, {'status': 'unaffected', 'version': '1.16.7', 'versionType': 'oss'}, {'status': 'unaffected', 'version': '1.15.13', 'versionType': 'enterprise support only'}, {'status': 'unaffected', 'version': '1.14.17', 'versionType': 'enterprise support only'}, {'status': 'unaffected', 'version': '1.9.19', 'versionType': 'enterprise support only'}], 'defaultStatus': 'affected'}] Added 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. When such unsafe instrumentation is used, the application becomes vulnerable to injection and spoofing attacks because micrometer-registry-statsd and micrometer-core do not sanitize newline characters (\n, \r) by default prior to this fix. * For the StatsD registry in micrometer-registry-statsd (when using the Datadog or Etsy flavor), because the StatsD protocol is newline-delimited, this allows for line-protocol injection (cross-metric spoofing). * For LoggingMeterRegistry in micrometer-core, because metric output is printed line-by-line to log files, this allows for both metric spoofing (if downstream log-metrics scrapers or parsers ingest the log lines as separate metrics) and general log spoofing. Specifically, an application is vulnerable when all the following are true: * The application uses a vulnerable version of io.micrometer:micrometer-registry-statsd or io.micrometer:micrometer-core. * The application uses the Datadog or Etsy flavor of the StatsD registry, or uses LoggingMeterRegistry. * The application instruments meters using user-controlled, unvalidated input for metric names, tag keys, or tag values. When vulnerable, an attacker can break out of the current metric or log line by injecting line terminators. This allows them to spoof arbitrary metrics (e.g., system load, standard JVM metrics, or other business metrics) across the metrics registry namespace (either directly via StatsD protocol or via downstream log-metric scrapers/parsers), as well as inject arbitrary log entries to spoof general log records. Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N Added Reference https://spring.io/security/cve-2026-59296