CVE & CISA-KEV Catalog

CVE-2026-78619

CRITICAL
9.8
CVSS v3
NVD

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploit Intelligence

0.62%probability of exploitation in 30 days
47thpercentile

Moderate risk: more likely to be exploited than 47% of all known CVEs.

References

Related Vulnerabilities

Other CWE-305 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2025-31161Critical9.8100%KEV + RansomFix
CVE-2020-10923High8.885%--
CVE-2023-28126Medium5.967%--
CVE-2023-34124Critical9.849%-Fix
CVE-2025-32011Critical9.827%--
CVE-2024-37085Medium6.827%KEV + RansomFix

Common questions

How do I fix CVE-2026-78619?

No published fix for CVE-2026-78619 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-78619 being actively exploited?

Not that we know of. CVE-2026-78619 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.62% is the estimated probability that it will be exploited in the next 30 days. That is higher than 47% of all scored CVEs.

How severe is CVE-2026-78619?

CVE-2026-78619 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-78619
CVE-2026-78619 severity badge

Markdown

[![CVE-2026-78619](https://tridentstack.com/cve/badge/CVE-2026-78619.svg)](https://tridentstack.com/cve/CVE-2026-78619)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-78619"><img src="https://tridentstack.com/cve/badge/CVE-2026-78619.svg" alt="CVE-2026-78619"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.