VMware Spring Micrometer up to 1.17.0 StatsD Registry/Logging Meter Registry injection

Summaryinfo

A vulnerability described as problematic has been identified in VMware Spring Micrometer up to 1.9.18/1.14.16/1.15.12/1.16.6/1.17.0. This impacts an unknown function of the component StatsD Registry/Logging Meter Registry. Executing a manipulation can lead to injection. The identification of this vulnerability is CVE-2026-59296. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic was found in VMware Spring Micrometer up to 1.9.18/1.14.16/1.15.12/1.16.6/1.17.0. This vulnerability affects an unknown code block of the component StatsD Registry/Logging Meter Registry. The manipulation with an unknown input leads to a injection vulnerability. The CWE definition for the vulnerability is CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. As an impact it is known to affect integrity. CVE summarizes:

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.

The advisory is shared for download at spring.io. This vulnerability was named CVE-2026-59296 since 07/04/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/21/2026). The MITRE ATT&CK project declares the attack technique as T1055.

Upgrading to version 1.9.19, 1.14.17, 1.15.13, 1.16.6.1, 1.16.7, 1.17.0.1 or 1.17.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-63885). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• VMware

Name

• Spring Micrometer

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.9.0
• 1.9.1
• 1.9.2
• 1.9.3
• 1.9.4
• 1.9.5
• 1.9.6
• 1.9.7
• 1.9.8
• 1.9.9
• 1.9.10
• 1.9.11
• 1.9.12
• 1.9.13
• 1.9.14
• 1.9.15
• 1.9.16
• 1.9.17
• 1.9.18
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.14.0
• 1.14.1
• 1.14.2
• 1.14.3
• 1.14.4
• 1.14.5
• 1.14.6
• 1.14.7
• 1.14.8
• 1.14.9
• 1.14.10
• 1.14.11
• 1.14.12
• 1.14.13
• 1.14.14
• 1.14.15
• 1.14.16
• 1.15
• 1.15.0
• 1.15.1
• 1.15.2
• 1.15.3
• 1.15.4
• 1.15.5
• 1.15.6
• 1.15.7
• 1.15.8
• 1.15.9
• 1.15.10
• 1.15.11
• 1.15.12
• 1.16
• 1.16.0
• 1.16.1
• 1.16.2
• 1.16.3
• 1.16.4
• 1.16.5
• 1.16.6
• 1.17.0

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion