dbcve.org
Datadog\Application · Binary

CVE-2026-11362

CRITICAL · 9.8 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 from event tags. DataDog::DogStatsd does not properly sanitise input, allowing metric injections of data from untrusted sources. The format_event method (used by the event method) does not validate the content of the tags, which may contain commas (allowing tags to be injected) or newlines, pipes and colons that allow metric injections. (There is an ineffective s/|//g to remove pipes, but because the pipe is not escaped, it is interpreted as a regular expression metacharacter and has no effect.)

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) fails to sanitize tag input in the format_event method. Specifically, tags are not validated, allowing commas (tag injection), newlines, pipes, and colons (metric injection). An attempted pipe removal regex (s/|//g) is ineffective because the unescaped pipe is interpreted as a regex metacharacter rather than a literal character, enabling injection attacks via untrusted metric data.

MitigationImplement strict input validation and proper escaping for all tag content in format_event, using quotemeta or equivalent to escape regex metacharacters and rejecting or sanitizing commas, newlines, and colons.

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
High

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

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. Verify DataDog::DogStatsd Perl module is installed
    Run 'perl -MDataDog::DogStatsd -e 'print DataDog::DogStatsd->VERSION . "\n"'' to check if the module loads and get its version number
    Affected if Module version is 0.07 or lower (or undef/empty which may indicate very old versions)
  2. Confirm the format_event method is in use
    Search codebase for calls to 'format_event' method, for example using grep: 'grep -r "format_event" --include="*.pl" --include="*.pm" .' or similar pattern matching
    Affected if The method format_event is being called in any Perl code that uses this library
  3. Inspect how tags parameter receives data
    Review the code paths that feed into the format_event tags argument; look for direct user input, external API data, or any data from untrusted sources being passed without validation
    Affected if Untrusted or user-supplied data flows into the tags parameter of format_event without sanitization
  4. Check for presence of faulty pipe regex in source
    If source code is available, search for the pattern 's/|//g' which incorrectly treats pipe as regex metacharacter rather than literal, indicating the vulnerable code path
    Affected if The faulty regex s/|//g is present in the format_event implementation, confirming the injection vulnerability exists

You are affected if you have DataDog::DogStatsd version 0.07 or lower AND use format_event with tags that contain data from untrusted or external sources.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.07
Interim mitigation

Implement strict input validation and proper escaping for all tag content in format_event, using quotemeta or equivalent to escape regex metacharacters and rejecting or sanitizing commas, newlines, and colons.

Recommended fix Moderate confidence

DataDog::DogStatsd version > 0.07 (latest stable CPAN release)

  1. Upgrade the DataDog::DogStatsd Perl module to a version greater than 0.07 using your Perl module manager (cpanm or similar): `cpanm DataDog::DogStatsd` or `cpanm DataDog::DogStatsd@latest`
  2. Verify the installed version is greater than 0.07: `perl -MDataDog::DogStatsd -e 'print $DataDog::DogStatsd::VERSION'"
  3. If automatic upgrade is not possible, manually install from CPAN: `cpan -i DataDog::DogStatsd`
  4. After upgrade, review application code that uses the event() or format_event() methods to ensure proper tag handling is now in place
  5. Test that metrics and events are being sent correctly to Datadog after the upgrade
Caveat Review release notes for any breaking changes between 0.07 and the new version; may require code changes if API changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datadog\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11362 — 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-11362 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