CVE-2026-35597: Vikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout

Severity: high (CVSS 7.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-04-10 · updated 2026-10-26
Weakness: CWE-307

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.

Affected products

go-vikunja vikunja: before 2.3.0 — fixed in 2.3.0

How to fix

Upgrade to a fixed version: go-vikunja vikunja 2.3.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-35597 or the next vulnerability affects your stack