CVE-2026-68581: Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision
Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Vikunjato a version that resolves this vulnerability.Fixed in 2.4.0 - Configuration
Ensure API token management validates the principal type when handling authenticated principal identity (principal type validation was missing/failed in Vikunja versions 0.22.0 through 2.3.0).
Vikunja API token management principal type validation = enabled
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68581?
The severity of CVE-2026-68581 is rated as high with a score of 8.1.
How do I fix CVE-2026-68581?
To fix CVE-2026-68581, update Vikunja to version 2.3.1 or later which addresses the authentication bypass issue.
What vulnerability does CVE-2026-68581 describe?
CVE-2026-68581 describes an authentication bypass vulnerability in Vikunja due to Principal ID collision between user IDs and link-share IDs.
Which versions of Vikunja are affected by CVE-2026-68581?
Vikunja versions 0.22.0 through 2.3.0 are affected by CVE-2026-68581.
What are the potential impacts of CVE-2026-68581?
CVE-2026-68581 can lead to unauthorized access to user accounts due to incorrect validation of API token management.