CVEvulnerability
CVE-2026-35597
7.5 HIGH
Official page ↗
- Status
- Analyzed
- Published
- 2026-04-10
- Last modified
- 2026-10-26
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 5.9 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CVSS 3.1 ([email protected])
- 7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- 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 configurations
• vikunja vikunja (< 2.3.0)
Related
Weakness · CWE (1)
- CWE-307 Improper Restriction of Excessive Authentication Attempts weakness
References
- https://github.com/go-vikunja/vikunja/commit/6ca0151d02fa0e8c7e2181ab916a28e08caaaec8 Patch
- https://github.com/go-vikunja/vikunja/pull/2576 Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv97-6cmj Exploit, Vendor Advisory
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv97-6cmj Exploit, Vendor Advisory