# CVE-2026-78619: Punk::Plugin::TOTP versions before 0.05 for Perl accept another account's recovery code at the two-factor challenge because totp_use_recover

> Attackers can bypass two-factor authentication by using their own recovery code to access other users' accounts due to flawed numeric identifier comparison.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-m82c-83jf-3j4v

## What is CVE-2026-78619?

CVE-2026-78619 is a critical authentication bypass vulnerability, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Punk::Plugin::TOTP versions before 0.05 for Perl accept another account's recovery code at the two-factor challenge because totp_use_recovery compares user identifiers numerically.

The helper searches the recovery model for the submitted code's digest alone, across every user's rows, so the ownership test that follows is the only thing binding a code to the account it was issued to. That test compares the row's user_id with the challenged user's id through Perl's integer coercion, and an identifier with no leading digits coerces to zero, so any two of them compare equal. User models keyed on a username, an email address or a UUID hit that case, and a numeric key compares as intended.

The challenge route feeds a submitted value to the helper once TOTP verification fails, so an attacker who knows a victim's password and holds a recovery code of their own passes the victim's second factor.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness), CWE-1025 (Comparison Using Wrong Factors)

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


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

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

## Is CVE-2026-78619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78619 is a critical authentication bypass vulnerability, published on 25 Aug 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-78619 in the wild and no public exploit code.

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-78619/ (Markdown: https://insights.sbomify.com/CVE-2026-78619/index.md)
```

## Sources

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

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