dbcve.org
Metrics\Application · Pevans

CVE-2026-50638

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 0.04 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 metrics, separated by newlines, to be sent per packet. Metrics::Any::Adapter::DogStatsd which extends Metrics::Any::Adapter::Statsd, which has a similar vulnerability. In addition, the _tags function does not check tags for newlines or statsd control characters. The tags can be used for metric injections.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Metrics::Any::Adapter::DogStatsd before version 0.04 fails to sanitize metric names and tags, allowing injection of arbitrary metrics via newlines or statsd control characters. Both the metric packet parsing and the _tags function accept unsanitized input, enabling attackers to manipulate or inject false metrics into monitoring systems.

MitigationUpgrade Metrics::Any::Adapter::DogStatsd to version 0.04 or later which implements proper sanitization of newlines and control characters in both metric names and tags.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Metrics\Application
Affected:< 0.04

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Metrics::Any::Adapter::DogStatsd
    Run: perl -MMetrics::Any::Adapter::DogStatsd -e 'print $Metrics::Any::Adapter::DogStatsd::VERSION'
    Affected if The version is missing or below 0.04 (e.g., 0.03, 0.02, or any version prior to 0.04)
  2. Locate the module file and verify version
    Find the module location with: perl -e 'foreach (@INC) { my $f = "$_/Metrics/Any/Adapter/DogStatsd.pm"; print "$f\n" if -f $f; }' then inspect the $VERSION variable in the file
    Affected if The module file does not exist or contains a version earlier than 0.04
  3. Check if application code uses Metrics::Any::Adapter::DogStatsd
    Search codebase for 'use Metrics::Any::Adapter::DogStatsd' or 'Metrics::Any::Adapter::DogStatsd->new' patterns in Perl source files
    Affected if The module is loaded and used in any Perl application within your environment
  4. Identify if metric names or tags are passed from external input
    Review application code that calls methods like 'counter', 'gauge', or 'distribution' from this adapter, checking whether user-controlled data flows directly to these metric methods
    Affected if External or user-supplied data is passed to metric name or tag parameters without prior sanitization of newlines or statsd control characters

Your environment is affected if Metrics::Any::Adapter::DogStatsd version 0.04 or later is NOT installed AND your application uses this module to emit metrics with external input in metric names or tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.04 or later
Fixed in 0.04
Interim mitigation

Upgrade Metrics::Any::Adapter::DogStatsd to version 0.04 or later which implements proper sanitization of newlines and control characters in both metric names and tags.

Recommended fix High confidence

Metrics::Any::Adapter::DogStatsd version 0.04

  1. Upgrade Metrics::Any::Adapter::DogStatsd to version 0.04 or later using your Perl module manager (e.g., cpanm Metrics::Any::Adapter::DogStatsd or cpan Metrics::Any::Adapter::DogStatsd)
  2. Verify the installed version matches or exceeds 0.04 by running: perl -MMetrics::Any::Adapter::DogStatsd -e 'print $Metrics::Any::Adapter::DogStatsd::VERSION'
  3. Test that your metrics collection continues to function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metrics\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50638 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50638 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data