# CVE-2026-46720: Net::Statsd::Tiny versions before 0.3.8 for Perl allowed metric injections

> Attackers can inject arbitrary statsd metrics via untrusted input due to missing validation of special characters in metric names and values.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 19 Jun 2026
- **Also known as:** GHSA-vqfg-jwcg-58ww

## What is CVE-2026-46720?

CVE-2026-46720 is a high-severity vulnerability in RRWO Net::Statsd::Tiny, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences), CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

## Which versions are affected by CVE-2026-46720?


## How do I fix CVE-2026-46720?

No fix has been published for CVE-2026-46720 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46720 being exploited?

There is no known exploitation of CVE-2026-46720 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46720 and fix it if it is affected.

What it is: CVE-2026-46720 is a high-severity vulnerability in RRWO Net::Statsd::Tiny, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46720 in the wild and no public exploit code.

Affected product: RRWO Net::Statsd::Tiny. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46720/ (Markdown: https://insights.sbomify.com/CVE-2026-46720/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46720
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46720
- OSV: https://osv.dev/vulnerability/CVE-2026-46720

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46720/
Summaries are generated and may contain mistakes; the official description above is the record.