CVE-2026-9270
Received Received - Intake
Metric Injection Vulnerability in DataDog DogStatsd Perl Library

Publication date: 2026-06-05

Last updated on: 2026-06-05

Assigner: CPANSec

Description
DataDog::DogStatsd versions through 0.07 for Perl allow metric injections. DataDog::DogStatsd does not properly sanitise input, allowing metric injections of data from untrusted sources. The send_stats method does not remove newlines from metric names ($stat variable), allowing attackers to change the metric name prefix. The send_stats method does not validate the content of the value ($delta variable), allowing attackers to inject metrics, especially from methods that do not restrict the data type for the value, such as set, gauge, count and histogram. The send_stats method does not validate the content of the tags, which may contain newlines, pipes and colons that allow metric injections. Note that the SYNOPSIS shows an example of passing a website form "loginName" parameter as a tag, which is unsafe.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-05
Last Modified
2026-06-05
Generated
2026-06-05
AI Q&A
2026-06-05
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
datadog dogstatsd to 0.07 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-93 The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
CWE-150 The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability affects DataDog::DogStatsd versions through 0.07 for Perl, where the software does not properly sanitize input, allowing metric injections from untrusted sources.

Specifically, the send_stats method fails to remove newlines from metric names, does not validate the content of the metric values, and does not validate tags, which can contain newlines, pipes, and colons. This allows attackers to manipulate metric names and inject arbitrary metrics.

An example given is passing a website form's "loginName" parameter as a tag, which is unsafe and can be exploited.


How can this vulnerability impact me? :

This vulnerability can allow attackers to inject malicious or misleading metrics into the monitoring system.

By manipulating metric names, values, and tags, attackers could corrupt monitoring data, potentially hiding real issues or creating false alerts.

This can lead to incorrect system monitoring, misinformed decision-making, and reduced trust in the monitoring infrastructure.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart