CVE-2026-68581

High

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.

SeverityHigh
CVSS8.1
Exploit probability—
ProductCode.vikunja.io/api
PublishedAug 2, 2026
First seenAug 2, 2026

How to fix

Affected products

ProductAffected versionsFixed in
code.vikunja.io/apiGo0.22.0 ≤ v < 2.4.0, 0.22.0 ≤ v2.4.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.