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_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.
Scoring
- Severity
- CRITICAL
- CVSS base score
- 9.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS probability
- 0.62%
- CWE
- CWE-305, CWE-1025
- Published
- 2026-08-25
- Last modified
- 2026-08-26
Weakness type
Related vulnerabilities
- CVE-2026-86207 — Authentication bypass leads to unauthorised access to N-central
- CVE-2026-81578 — PaperCut MF/NG: Authentication Bypass
- CVE-2026-16895 — Authentication Bypass in Metasploit JSON-RPC Service When DB Health Check Fails
- CVE-2026-53561 — Apache Hive: Unauthenticated authentication bypass in HiveServer2 HTTP SAML bearer-token validation allows impersonation of any Hive user
- CVE-2025-14600 — Admin Account Takeover via Path Traversal in vsDesk
- CVE-2026-19349 — Lemonldap::NG::Portal versions from 2.0.0 before 2.16.9, from 2.17.0 before 2.21.5, from 2.22.0 before 2.23.3 for Perl allow authentication bypass via an OAuth2 state parameter stored as an SSO session in the GitHub and LinkedIn backends
- CVE-2026-1621 — Register Bypass in Universal Sotware's E-Municipality
- CVE-2026-65935 — Bypassing passkey entry in legacy pairing