CVE-2026-35597

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

Published Apr 10, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An in‑memory counter records TOTP failures, but the lockout state is not persisted because a database rollback undoes the status change. When an attacker supplies an incorrect TOTP code, the account never locks, allowing unlimited attempts to guess a correct code. This flaw permits brute‑force authentication of two‑factor protected accounts. The weakness is captured by CWE‑307 and results in elevated access without valid second factor, leading to potential unauthorized data exposure and modification.

Affected Systems

The issue affects the Vikunja task‑management platform, provided by the go‑vikunja organization. Any deployment of Vikunja version 2.2.x or earlier is vulnerable. The problem is resolved in release 2.3.0 and later. Users running earlier versions on external servers or internal infrastructure are at risk.

Risk and Exploitability

The CVSS base score of 5.9 indicates moderate severity. No EPSS information is available, and the vulnerability is not listed in the CISA KEV catalog. Because the flaw operates during the login phase, it can be exploited over the network when an attacker can supply a username and repeated TOTP attempts, or locally if the attacker can guess a valid username. The attack vector is therefore likely remote network login or local compromise, and an attacker can gain access after sufficient failed TOTP attempts because the lockout never persists.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Vikunja to version 2.3.0 or later to apply the patch that correctly persists account lockout status.
  • If an upgrade cannot be performed immediately, monitor authentication logs for excessive TOTP failures and temporarily block accounts that exceed a threshold.
  • Consider disabling two‑factor authentication for critical accounts until the update is applied, or enforce stricter rate‑limiting on login attempts.

Generated by OpenCVE AI on April 10, 2026 at 17:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fgfv-pv97-6cmj Vikunja Vulnerable to TOTP Brute-Force Due to Non-Functional Account Lockout
History
Type Values Removed Values Added
First Time appeared Vikunja
Vikunja vikunja
CPEs cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
Vendors & Products Vikunja
Vikunja vikunja
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Go-vikunja
Go-vikunja vikunja
Vendors & Products Go-vikunja
Go-vikunja vikunja
Type Values Removed Values Added
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.
Title Vikunja Affected by TOTP Brute-Force Due to Non-Functional Account Lockout
Weaknesses CWE-307
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-307

    Improper Restriction of Excessive Authentication Attempts

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 13, 2026, 3:37 PM
Reserved
Apr 3, 2026, 9:25 PM
Status
Analyzed
Published
Apr 10, 2026, 5:17 PM
Modified
Oct 26, 2026, 10:10 PM