# CVE-2026-45180: Catalyst::Plugin::Statsd versions through 0.10.0 for Perl may leak session ids

> Attackers can steal session IDs if the statsd communication channel is unsecured, potentially leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2026
- **Updated:** 12 May 2026

## What is CVE-2026-45180?

CVE-2026-45180 is a high-severity vulnerability in RRWO Catalyst::Plugin::Statsd, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Catalyst::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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2026-45180?


## How do I fix CVE-2026-45180?

No fix has been published for CVE-2026-45180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45180 being exploited?

There is no known exploitation of CVE-2026-45180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45180 and fix it if it is affected.

What it is: CVE-2026-45180 is a high-severity vulnerability in RRWO Catalyst::Plugin::Statsd, published on 10 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45180 in the wild and no public exploit code.

Affected product: RRWO Catalyst::Plugin::Statsd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45180/ (Markdown: https://insights.sbomify.com/CVE-2026-45180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45180
- OSV: https://osv.dev/vulnerability/CVE-2026-45180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45180/
Summaries are generated and may contain mistakes; the official description above is the record.