dbcve.org
Datadog\Application · Binary

CVE-2026-9270

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to after 0.07 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The DataDog::DogStatsd Perl library (versions through 0.07) lacks input sanitization in its send_stats method, allowing metric injection attacks. Specifically, newlines in metric names enable prefix manipulation, unvalidated values allow arbitrary metric injection via set/gauge/count/histogram methods, and tags accept newlines/pipes/colons that can corrupt metric data. User-supplied input like form parameters is directly used without validation.

MitigationImplement strict input validation and sanitization for all user-controlled parameters (metric names, values, and tags) by stripping or rejecting newlines, pipes, and colons before passing data to send_stats. Treat all external input as untrusted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Datadog\Application
Affected:<= 0.07

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if DataDog::DogStatsd Perl module is installed
    Run 'perldoc -l DataDog::DogStatsd' or 'perl -MDataDog::DogStatsd -e 'print $DataDog::DogStatsd::VERSION.''
    Affected if Module is not found or not installed
  2. Determine the installed version of DataDog::DogStatsd
    Run 'perl -MDataDog::DogStatsd -e 'print $DataDog::DogStatsd::VERSION.'' and compare to 0.07
    Affected if Version is 0.07 or lower
  3. Identify Perl scripts using DataDog::DogStatsd
    Search codebase for 'use DataDog::DogStatsd' or 'DataDog::DogStatsd->new' statements
    Affected if No usage found indicates not affected
  4. Inspect metric submission calls for unsanitized user input
    Review code that calls $dogstatsd->count(), $dogstatsd->gauge(), $dogstatsd->set(), $dogstatsd->histogram() or send_stats() and check if user-supplied variables are passed directly to metric name, value, or tag parameters
    Affected if User-controlled variables are passed directly to metric methods without sanitization for newlines, pipes, or colons
  5. Check if tag parameters accept unvalidated input
    Examine code paths where tags array parameter is populated from user input, HTTP headers, or file content without filtering special characters
    Affected if Tags are constructed from untrusted input without validation

A system is affected if DataDog::DogStatsd version 0.07 or lower is installed AND code passes unsanitized user input to metric names, values, or tag parameters in DogStatsd method calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.07
Interim mitigation

Implement strict input validation and sanitization for all user-controlled parameters (metric names, values, and tags) by stripping or rejecting newlines, pipes, and colons before passing data to send_stats. Treat all external input as untrusted.

Fix this in Datadog\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9270 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data