CVE-2026-68581

HIGH

Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision

Title source: cna
STIX 2.1

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.

References (4)

Core 4
Core References
Vendor Advisory vendor-advisory
GitHub Security Advisory (GHSA-vvcv-vpph-h844)
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-vvcv-vpph-h844
Third Party Advisory third-party-advisory
VulnCheck Advisory: Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision
https://www.vulncheck.com/advisories/vikunja-through-authentication-bypass-via-principal-id-collision

Scores

CVSS v3 8.1
EPSS 0.0032
EPSS Percentile 24.5%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CISA SSVC

Vulnrichment
Exploitation poc
Automatable no
Technical Impact total

Details

CWE
CWE-863
Status published
Products (1)
go-vikunja/vikunja 0.22.0 - 2.4.0
Published Aug 02, 2026
Tracked Since Aug 02, 2026