CVE-2026-68581

published 2 Aug 2026 · updated 3 Aug 2026

Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision

8.1HighCVSS 8.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.4.0.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
go-vikunja>=0.22.0 <2.4.02.4.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-68581 severity on Zeptric[![CVE-2026-68581](https://zeptric.io/badge/cve/CVE-2026-68581.svg)](https://zeptric.io/cve/CVE-2026-68581)