Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/routes/api/v1/login.go calls HandleFailedTOTPAuth and then unconditionally rolls back. HandleFailedTOTPAuth in pkg/user/totp.go uses an in-memory counter (key-value store) to track failed attempts. When the counter reaches 10, it calls user.SetStatus(s, StatusAccountLocked) on the same database session s. Because the login handler always rolls back after a TOTP failure, the StatusAccountLocked write is undone. The in-memory counter correctly increments past 10, so the lockout code executes on every subsequent attempt, but the database write is rolled back every time. This allows unlimited brute-force attempts against TOTP codes. This vulnerability is fixed in 2.3.0.
INFO
Published Date :
2026-04-10T16:03:19.636Z
Last Modified :
2026-04-13T15:37:11.358Z
Source :
GitHub_M
AFFECTED PRODUCTS
The following products are affected by CVE-2026-35597 vulnerability.
| Vendors | Products |
|---|---|
| Go-vikunja |
|
| Vikunja |
|
REFERENCES
Here, you will find a curated list of external links that provide in-depth information to CVE-2026-35597.
