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.
{
"cna_assigner": "VulnCheck",
"cwe_ids": [
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68581.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0.22.0"
},
{
"fixed": "2.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "e6b25bd57b537ef9a72b5acdadf446ca5ef77bfa"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "95b7e673fb5ee407498fa4b13e8b4c57847a4a0b"
}
],
"source": "REFERENCES_COMMIT"
}
]
}