Trending
CVE-2026-50637

CVE detail

CVE-2026-50637

Metrics::Any::Adapter::Statsd versions before 0.04 for Perl does not protect against metric injections. The statsd protocol (and extensions) allow mutiple metrics, separated by newlines, to be sent per packet. The send method does not validate the contents of the metric names or values. If the names have newlines and statsd control characters (colon, pipe) then metric injections are possible. Version 0.04 fixed this by modifying the _make method to block metric names with characters below ASCII 32 (which includes the newline), or colons or pipes.

CVSS 8.2 · HighBuzz score 29.5

Buzz score

Why this CVE is surfacing

Buzz score total 29.5

This all-time snapshot uses the same composite formula as Trending across a 30-year evidence window, rather than a current rolling window.

Buzz score components · mention 19.5 · diversity 10.0 · KEV 0.0 · OTX 0.0 · PoC 0.0

Mention score

19.5

6 evidence mentions in the snapshot

Diversity score

10.0

2 sources across 2 categories

KEV score

0.0

No KEV entry observed

OTX score

0.0

0 OTX pulses

PoC score

0.0

0 repos · best confidence N/A

Best PoC traction

Maximum stars on a matched PoC repo

Why it matters now

Mention timeline

Total mentions: 0; within the 30d window
Peak daily: 0; highest bucket

Evidence

Source links by recency

Newest mentions first

6 source links · newest first

https://www.cve.org/CVERecord?id=CVE-2026-50639www.cve.org
No excerpt available.
Third Party Advisorywww.cve.orgJun 10, 2026, 7:16 PM
https://www.cve.org/CVERecord?id=CVE-2026-50638www.cve.org
No excerpt available.
Third Party Advisorywww.cve.orgJun 10, 2026, 7:16 PM
https://www.cve.org/CVERecord?id=CVE-2026-46739www.cve.org
No excerpt available.
Third Party Advisorywww.cve.orgJun 10, 2026, 7:16 PM
https://www.cve.org/CVERecord?id=CVE-2026-46720www.cve.org
No excerpt available.
Third Party Advisorywww.cve.orgJun 10, 2026, 7:16 PM
https://www.cve.org/CVERecord?id=CVE-2026-46719www.cve.org
No excerpt available.
Third Party Advisorywww.cve.orgJun 10, 2026, 7:16 PM
https://metacpan.org/release/PEVANS/Metrics-Any-Adapter-Statsd-0.04/changesmetacpan.org
No excerpt available.
Release Notesmetacpan.orgJun 10, 2026, 7:16 PM

Exploit code

Public exploit repository references

Public PoC repositories are third-party, potentially unsafe artifacts. Treat their code as untrusted and use it only on authorized systems in an isolated, least-privilege environment. cvebuzz does not execute the code or verify that an exploit works.

0 repository references · best confidence N/A · max 0 stars

No public PoC repositories have been matched yet.

Related records

Similar CVEs

6 related CVEs with shared weakness or product evidence

CVE-2026-11373
Net::Statsite::Client versions through 1.1.0 for Perl allow metric injections. Net::Statsite::Client is a client for the statsite protocol, which is a variant of statsd. Newline…
CVSS 9.1 · Critical
6 mentions
CVE-2026-50639
Metrics::Any::Adapter::SignalFx versions before 0.04 for Perl does not protect against metric injections. The statsd protocol (and extensions such as dogstatsd) allow mutiple met…
CVSS 6.5 · Medium
4 mentions
CVE-2026-50638
Metrics::Any::Adapter::DogStatsd versions before 0.04 for Perl does not protect against metric injections. The statsd protocol (and extensions such as dogstatsd) allow mutiple me…
CVSS 9.1 · Critical
4 mentions
CVE-2026-9270
DataDog::DogStatsd versions through 0.07 for Perl allow metric injections. DataDog::DogStatsd does not properly sanitise input, allowing metric injections of data from untrusted…
CVSS 9.1 · Critical
3 mentions
CVE-2026-11362
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…
CVSS 9.8 · Critical
3 mentions
CVE-2026-46741
Etsy::StatsD versions through 1.002002 for Perl allow metric injections. The metric names and values are not checked for newlines, colons or pipes. Metrics generated from untrust…
CVSS 7.5 · High
2 mentions

External lookup

Potential internet exposure

Potential exposure only — not proof of vulnerability.Shodan results indicate potentially internet-exposed products, not confirmed vulnerable systems. They do not confirm that any returned system is vulnerable to CVE-2026-50637.

Product-level CPE searches intentionally omit version fields and NVD version-range or configuration certainty. Verify the exact product version and configuration independently.

Sign-in required. Shodan requires you to sign in to run these filter searches.

Product CPE queries

Derived from this CVE's existing NVD CPE 2.3 records; the application, operating-system, or hardware part is retained.

cpe:2.3:a:pevans:metrics\:\:any\:\:adapter\:\:statsdSearch this product on Shodan

Exact CVE query

Eligible paid Shodan plan required

Shodan's exact vuln: filter is separate from the product searches above and requires an eligible paid Shodan plan.

vuln:CVE-2026-50637Search this CVE on Shodan

These are outbound search links only. cvebuzz makes no Shodan API call, uses no Shodan API key, and does not display live result counts.

Metadata

Canonical fields

NVD status

Analyzed

Published

Jun 10, 2026

Modified

Jun 24, 2026

Official record

Authoritative NVD record

CVSS vector

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

CWE IDs

Vendor classifications

How this vector reads

CVSS 3.1 base metrics decoded below. This explanation does not recalculate or change the NVD score.

Attack Vector (AV): Network. The vulnerable system can be reached across network boundaries.
Attack Complexity (AC): Low. No special conditions beyond the attacker-controlled steps are required.
Privileges Required (PR): None. The attacker needs no privileges on the vulnerable system.
User Interaction (UI): None. Exploitation does not require another user to act.
Scope (S): Unchanged. Impacts remain within the vulnerable security authority.
Confidentiality Impact (C): Low. There is a limited impact to this security property.
Integrity Impact (I): High. There is a total or serious impact to this security property.
Availability Impact (A): None. There is no direct impact to this security property.

Signals

Exploitation indicators

0 stored signals · no KEV · 0 OTX pulses