CVE-2026-59296
Received Received - Intake

StatsD Protocol Injection in Micrometer StatsD Registry

Vulnerability report for CVE-2026-59296, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-21

Last updated on: 2026-08-21

Assigner: VMware

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-21
Last Modified
2026-08-21
Generated
2026-08-21
AI Q&A
2026-08-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
micrometer micrometer-registry-statsd From 1.14.0 (inc) to 1.17.0 (inc)
micrometer micrometer-core From 1.14.0 (inc) to 1.17.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-59296 is a vulnerability in Micrometer's StatsD and Logging meter registries where untrusted input for metric names, tag keys, or tag values is not sanitized. This allows attackers to inject newline characters, enabling metric spoofing or log manipulation. The issue affects applications using vulnerable versions of micrometer-registry-statsd (Datadog or Etsy flavors) or micrometer-core (LoggingMeterRegistry).

Detection Guidance

Check if your application uses vulnerable versions of micrometer-registry-statsd (Datadog or Etsy flavors) or micrometer-core with LoggingMeterRegistry. Inspect metric names, tag keys, or tag values for newline characters in logs or StatsD output. Use commands like grep to search for newline characters in application logs or metrics output.

Impact Analysis

An attacker could spoof arbitrary metrics by injecting line terminators, affecting metrics like system load or business metrics. For LoggingMeterRegistry, they could inject fake log entries. Exploitation requires user-controlled, unvalidated input for metrics or logs.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by enabling log spoofing and metric injection. Attackers could manipulate log entries to falsify records, potentially violating audit requirements under HIPAA for accurate logging. For GDPR, injected metrics or logs might expose or alter sensitive data processing information, undermining accountability and data integrity principles.

Mitigation Strategies

Upgrade to the latest fixed versions of Micrometer (e.g., 1.17.1, 1.16.7, or 1.15.13). Avoid using user-controlled input for metric names, tag keys, or tag values without validation. Sanitize all inputs to remove newline characters before processing.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59296. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart