CVE-2026-32729: Runtipi has a TOTP two-factor authentication bypass via unrestricted brute-force on `/api/auth/verify-totp`
Runtipi is a personal homeserver orchestrator. Prior to 4.8.1, The Runtipi /api/auth/verify-totp endpoint does not enforce any rate limiting, attempt counting, or account lockout mechanism. An attacker who has obtained a user's valid credentials (via phishing, credential stuffing, or data breach) can brute-force the 6-digit TOTP code to completely bypass two-factor authentication. The TOTP verification session persists for 24 hours (default cache TTL), providing an excessive window during which the full 1,000,000-code keyspace (000000–999999) can be exhausted. At practical request rates (~500 req/s), the attack completes in approximately 33 minutes in the worst case. This vulnerability is fixed in 4.8.1.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32729?
CVE-2026-32729 is considered a high severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2026-32729?
To fix CVE-2026-32729, update Runtipi to version 4.8.1 or later, which implements proper rate limiting.
What kind of attack does CVE-2026-32729 allow?
CVE-2026-32729 allows attackers to brute-force the TOTP verification process due to lack of rate limiting and account lockout.
Which versions of Runtipi are affected by CVE-2026-32729?
All versions of Runtipi prior to 4.8.1 are affected by CVE-2026-32729.
Is there a workaround for CVE-2026-32729 if I cannot update immediately?
There is no official workaround for CVE-2026-32729; upgrading to a secure version is the recommended approach.