CVE-2026-46720: Net::Statsd::Tiny versions before 0.3.8 for Perl allowed metric injections
Net::Statsd::Tiny versions before 0.3.8 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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46720 affects the Perl Net::Statsd::Tiny library before 0.3.8. If an application builds StatsD metric names or set values from untrusted input, that input could create extra fake metrics. This can corrupt monitoring data and mislead operational or security decisions.
Executive priority
Prioritize remediation for systems where monitoring integrity affects incident response, billing, reliability alerts, or executive reporting. This is high severity but evidence of active exploitation was not provided.
Technical view
Net::Statsd::Tiny did not validate newline, colon, or pipe characters in metric names and set values. Untrusted input used in metric generation could inject additional StatsD metrics. The CVE lists CVSS 8.2 high, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely in Perl applications using Net::Statsd::Tiny before 0.3.8 and passing user-controlled or external data into metric names or set values.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Abuse would depend on application-specific use of untrusted input in StatsD metric construction.
Researcher notes
The vulnerability maps to improper neutralization of delimiters and CRLF-style injection concerns, listed as CWE-150 and CWE-93. Related CVE-2026-46719 may be relevant for reviewing adjacent fixes, but this analysis only covers CVE-2026-46720.
Mitigation direction
Upgrade Net::Statsd::Tiny to version 0.3.8 or later.
Review vendor release notes and patch details for the validation change.
Avoid using untrusted input directly in metric names or set values.
Add application-side validation for metric components where appropriate.
Validation and detection
Inventory Perl dependencies for Net::Statsd::Tiny usage.
Confirm installed Net::Statsd::Tiny versions are 0.3.8 or later.
Search code for untrusted input used in metric names or set values.
Review monitoring data paths for metrics sourced from external requests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-150: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-150 · source CWE mapping
Improper Neutralization of Escape, Meta, or Control Sequences
Improper Neutralization of Escape, Meta, or Control Sequences represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of CRLF Sequences ('CRLF Injection')
Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.