CVE-2026-32729
2FA bypass via brute-forcing TOTP on Runtipi API before 4.8.1; 24h session TTL.
Is CVE-2026-32729 being exploited?
Not confirmed. CVE-2026-32729 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-32729?
CVE-2026-32729 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32729?
Yes. A fix has been recorded for CVE-2026-32729. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32729 affect?
CVE-2026-32729 affects Runtipi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32729?
Upgrade to 4.8.1+; enable rate limiting; rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypasses 2FA by brute-forcing TOTP; 24h session TTL provides long window for account compromise.
Patch when possible
- affected< 4.8.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.