Skip to content

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

HighCVSS 7.5 EPSS 0.31%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial

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.

Upgrade path

3 packages: 1 fixed, 1 partially fixed.

PackageAffectedFixed inStatus
code.vikunja.io/api(Go) < 2.3.0; <= 2.2.2; All versions 2.3.0 Partially fixed
vikunja < 2.3.0 2.3.0 Fixed
go-vikunja vikunja = < 2.3.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
code.vikunja.io/api(Go) < 2.3.0 2.3.0
code.vikunja.io/api(Go) All versions No fix listed
go-vikunja vikunja = < 2.3.0 No fix listed
code.vikunja.io/api(Go) <= 2.2.2 No fix listed
vikunja < 2.3.0 2.3.0

References