CVE-2026-68581

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-02 13:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-23 22:10 UTC Last updatedMost recent change to the record

Details

Published

2026-08-02 13:16 UTC

Last modified

2026-10-23 22:10 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Deferred

Attack profile CVSS 4.0 · 8.6

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

High

Integrity

High

Availability

None