Cyber Resilience

CVE-2026-11362

Binary Datadog\ \

Published
05 June 2026
Modified
17 June 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0045 37th percentile
Risk Priority 71 floored blend · peak EPSS

Summary

CVE-2026-11362 is a critical-severity CRLF Injection (CWE-93) vulnerability in Binary Datadog\. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

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.)

CWE(s)
CWE-93CWE-150

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-9270Same product: Binary Datadog\
CVE-2026-46740Shared CWE-150, CWE-93
CVE-2026-46741Shared CWE-150, CWE-93
CVE-2026-8788Shared CWE-150, CWE-93
CVE-2026-23829Shared CWE-150, CWE-93
CVE-2026-50638Shared CWE-150, CWE-93
CVE-2026-50639Shared CWE-150, CWE-93
CVE-2026-11373Shared CWE-150, CWE-93
CVE-2026-46719Shared CWE-150, CWE-93
CVE-2026-46739Shared CWE-150, CWE-93

Affected Assets

binary
datadog\
\

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10
  • V1.3.12
  • V4.2.4

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly stops untrusted data containing CRLF sequences from reaching the component that treats CRLF as a delimiter.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to block CRLF injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect CRLF flaws but does not itself implement the neutralization.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing special characters such as CRLF in inputs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe handling of untrusted data but do not prescribe specific CRLF controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require neutralization of CRLF sequences, fully addressing this weakness.

References