# CVE-2026-5091: Catalyst::Plugin::Authentication versions through 0.10024 for Perl is susceptible to timing attacks

> Attackers can exploit timing discrepancies in password comparison to guess hashes or passwords in the Catalyst authentication plugin.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2026
- **Updated:** 22 May 2026
- **Also known as:** DEBIAN-CVE-2026-5091, GHSA-37jv-v9vv-wxwv, MGASA-2026-0160, UBUNTU-CVE-2026-5091

## What is CVE-2026-5091?

CVE-2026-5091 is a medium-severity vulnerability in JJNAPIORK Catalyst::Plugin::Authentication, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Catalyst::Plugin::Authentication versions through 0.10024 for Perl  is susceptible to timing attacks.

These versions use Perl's built-in eq comparison. Discrepencies in timing could be used to guess the underlying hash or password.

Weakness: CWE-208 (Observable Timing Discrepancy)

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


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

Apply the vendor's patch.

## Is CVE-2026-5091 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5091 is a medium-severity vulnerability in JJNAPIORK Catalyst::Plugin::Authentication, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5091 in the wild and no public exploit code.

Affected product: JJNAPIORK Catalyst::Plugin::Authentication. 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-5091/ (Markdown: https://insights.sbomify.com/CVE-2026-5091/index.md)
```

## Sources

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

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