CVE-2026-68581 Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision
- Published
- Updated
- Exploit status
- No public exploit known
Description
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 products
| Product | Affected versions | Fixed in |
|---|---|---|
| code.vikunja.io/api | >= 0.22.0, < 2.4.0 | 2.4.0 |
| code.vikunja.io/api(Go) | >= 0.22.0, < 2.4.0 | 2.4.0 |
| code.vikunja.io/api(Go) | >= 0.22.0 | No fix listed |
| code.vikunja.io/api(Go) | >= 0.22.0, <= 2.3.0 | No fix listed |
References
- GitHub Security Advisory (GHSA-vvcv-vpph-h844) exploit vendor-advisory
- Patch Commit patch
- Patch Commit patch
- VulnCheck Advisory: Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision third-party-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com product
- github.com
- github.com