dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2026-45179

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Plack::Middleware::Statsd versions before 0.9.0 for Perl may leak user IP addresses. If the communication channel to the statsd daemon is not secured (for example, by sending UDP packets to a host on another network), then users' IP addresses may be leaked. Since version 0.9.0, the IP address is no longer logged to statsd unless configured. When configured, an HMAC signature of the IP address is logged instead.

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

Plack::Middleware::Statsd versions before 0.9.0 for Perl logs user IP addresses to a statsd daemon. When the statsd communication channel is unsecured (e.g., UDP packets to a host on another network), these IP addresses can be intercepted and leaked, compromising user privacy.

MitigationUpgrade Plack::Middleware::Statsd to version 0.9.0 or later, which defaults to not logging IP addresses and uses HMAC-signed hashes when configured. Alternatively, ensure statsd communication is secured via authenticated/encrypted channels.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Plack::Middleware::Statsd version
    Run 'perl -MPlack::Middleware::Statsd -e 'print $Plack::Middleware::Statsd::VERSION' or check your cpanfile/cpanfile.snapshot for the version pinned, or use 'cpanm --look Plack::Middleware::Statsd' to inspect the installed module version
    Affected if Version is below 0.9.0 or the module is not found (indicating an older release may be in use)
  2. Verify the middleware is enabled in your Plack application
    Inspect your PSGI application file or Plack configuration (e.g., app.psgi, builder.pl) for 'enable "Statsd"' or 'enable "Plack::Middleware::Statsd"' statements
    Affected if The middleware is loaded and active in your application stack
  3. Inspect statsd transport configuration
    Check your Plack app configuration for statsd server settings - look for host/port parameters passed to the middleware (e.g., statsd_host => 'x.x.x.x', statsd_port => 8125) and determine if UDP is being used
    Affected if Statsd is configured to send metrics to a remote host over UDP (unencrypted transport)
  4. Check for IP address inclusion in metrics
    Review your statsd middleware configuration for options like 'include_ip => 1' or similar settings that would include client IP in metric labels, and verify what metrics are being sent
    Affected if IP-related metrics are being transmitted to a remote statsd daemon over unsecured transport

You are affected if Plack::Middleware::Statsd version is below 0.9.0 AND the middleware is actively sending IP-related metrics to a remote statsd server over unencrypted UDP transport.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Plack::Middleware::Statsd to version 0.9.0 or later, which defaults to not logging IP addresses and uses HMAC-signed hashes when configured. Alternatively, ensure statsd communication is secured via authenticated/encrypted channels.

Recommended fix Moderate confidence

0.9.0

  1. Check your current Plack::Middleware::Statsd version by examining your cpanfile, cpanfile.snapshot, or by running 'cpan -D Plack::Middleware::Statsd'
  2. If you are running a version before 0.9.0, upgrade the module by running 'cpanm Plack::Middleware::Statsd' or 'cpan Plack::Middleware::Statsd'
  3. After upgrading, verify the new version is installed: 'cpan -D Plack::Middleware::Statsd'
  4. If you need to log IP addresses for legitimate metrics purposes, configure the HMAC signing feature in version 0.9.0+ to avoid leaking plaintext IPs
  5. Ensure your statsd daemon communication channel is secured (e.g., use DTLS for UDP or TLS for TCP) if transmitting over untrusted networks

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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