dbcve.org
Metrics\Application · Pevans

CVE-2026-50639

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 0.04 or later.
See remediation →
74/100
Remediation priority · Elevated
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::SignalFx 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::SignalFx which extends Metrics::Any::Adapter::Statsd, which has a similar vulnerability. In addition, the _labels function does not check tags labels newlines or statsd control characters. The labels 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 · moderate confidence

Metrics::Any::Adapter::SignalFx before version 0.04 fails to sanitize labels/tags for newlines and statsd control characters, allowing attackers to inject arbitrary metrics via crafted label values. The vulnerability stems from the _labels function not validating input and the underlying statsd protocol's support for multiple metrics per packet separated by newlines.

MitigationUpdate to Metrics::Any::Adapter::SignalFx version 0.04 or later, which implements proper input validation to strip or reject newlines and control characters in labels.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check installed version of Metrics::Any::Adapter::SignalFx
    Run `perl -MMetrics::Any::Adapter::SignalFx -e 'print $Metrics::Any::Adapter::SignalFx::VERSION'` or use `perldoc -l Metrics::Any::Adapter::SignalFx` to find the module location and inspect the $VERSION variable
    Affected if The command returns a version lower than 0.04 or reports the module as not found (not installed)
  2. Verify the module is actually loaded and in use
    Search your application code for 'use Metrics::Any::Adapter::SignalFx' or 'Metrics::Any::Adapter::SignalFx->new' to confirm the module is being instantiated
    Affected if The module is loaded in your application with a version below 0.04
  3. Determine if custom labels/tags are being passed to the module
    Review your application code for calls that pass label or tag parameters to metrics, such as $adapter->make_counter(... labels => {...}) or $adapter->make_gauge(... tags => [...])
    Affected if Your code passes externally-sourced or user-controllable values as labels or tags to any Metrics::Any metric

You are affected if Metrics::Any::Adapter::SignalFx version 0.04 or earlier is installed AND your application passes custom label values (especially from external sources) to metrics.

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

Update to Metrics::Any::Adapter::SignalFx version 0.04 or later, which implements proper input validation to strip or reject newlines and control characters in labels.

Recommended fix High confidence

Metrics::Any::Adapter::SignalFx version 0.04

  1. Use cpanm to upgrade the module: cpanm Metrics::Any::Adapter::SignalFx
  2. Or use cpan: cpan -i Metrics::Any::Adapter::SignalFx
  3. Verify the installed version: perl -MMetrics::Any::Adapter::SignalFx -e 'print $Metrics::Any::Adapter::SignalFx::VERSION'

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

Fix this in Metrics\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50639 — 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-50639 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