CVE-2026-45180
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 · uneditedCatalyst::Plugin::Statsd versions through 0.10.0 for Perl may leak session ids. 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' session ids may be leaked. This may allow an attacker to use session ids as authentication tokens.
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 confidenceCatalyst::Plugin::Statsd versions through 0.10.0 sends session IDs to a statsd monitoring daemon via UDP or another unencrypted protocol. When the statsd destination is on an untrusted network, attackers can intercept these session IDs and use them as authentication tokens to hijack user sessions.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Catalyst::Plugin::Statsd is installedRun `perl -MCatalyst::Plugin::Statsd -e 'print $Catalyst::Plugin::Statsd::VERSION . "\n"'` to get the installed version, or list the module via your system's Perl package managerAffected if The version is 0.10.0 or lower
-
Verify the plugin is loaded in your Catalyst applicationSearch your application configuration files (such as MyApp.pm or myapp.conf) for 'Catalyst::Plugin::Statsd' or 'Statsd' in the plugin configuration sectionAffected if The plugin is explicitly loaded in your Catalyst application configuration
-
Identify the configured statsd serverExamine your application configuration for statsd host and port settings (typically keys like 'statsd' or 'statsd_host' under the plugin configuration)Affected if A statsd host is configured that points to a remote IP address rather than localhost or 127.0.0.1
-
Check the statsd transport mechanismReview how your application sends statsd metrics; if UDP is used to a remote host across the network, the communication is unsecuredAffected if Metrics are being sent via UDP to a non-localhost destination
You are affected if Catalyst::Plugin::Statsd version 0.10.0 or lower is loaded in your application and configured to send session IDs to a remote statsd server over an unsecured network path.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRoute statsd traffic exclusively to localhost, or implement TLS/encrypted transport for statsd communications; alternatively, modify the plugin to hash or exclude session IDs from metrics.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45180 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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