CVE-2026-50637: Pevans Metrics::any::adapter::statsd vulnerability (CVSS 8.2)

Description

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 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityLow

IntegrityHigh

AvailabilityNone

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

Affected products

Pevans Metrics::any::adapter::statsd< 0.04

Remediation

Fixed in

Pevans Metrics::any::adapter::statsd≥ 0.04

References

https://metacpan.org/release/PEVANS/Metrics-Any-Adapter-Statsd-0.04/changesRelease Notes
https://www.cve.org/CVERecord?id=CVE-2026-46719Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2026-46720Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2026-46739Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2026-50638Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2026-50639Third Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-50637 being actively exploited?

CVE-2026-50637 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.50%.

How severe is CVE-2026-50637?

CVE-2026-50637 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.50% probability of exploitation.

Which products are affected by CVE-2026-50637?

Affected products include Pevans Metrics::any::adapter::statsd.

How do I fix CVE-2026-50637?

Upgrade affected software to a fixed version, for example Pevans Metrics::any::adapter::statsd 0.04 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-50637 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo