Cyber Resilience

CVE-2026-46740

Published
26 May 2026
Modified
24 July 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0033 25th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2026-46740 is a medium-severity CRLF Injection (CWE-93) vulnerability. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 25th 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

Mojolicious::Plugin::Statsd versions through 0.04 for Perl allowed metric injections. The metric names and set values were not checked for newlines, colons or pipes. Metrics generated from untrusted sources could inject additional statsd metrics. Version 0.06 changes the module from being…

more

a statsd client to using a separate statsd client. It defaults to using a version of Net::Statsd::Tiny that fixes a similar issue (CVE-2026-46720).

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-9270Shared 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
CVE-2026-50637Shared CWE-150, CWE-93

Affected Assets

—
Statsd
inferred from references and description; NVD did not file a CPE for this CVE

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