go-vikunja up to 2.3.0 API Token Management /api/v1/tokens web.Auth.GetID privileges management

Summaryinfo

A vulnerability identified as critical has been detected in go-vikunja vikunja up to 2.3.0. The impacted element is the function web.Auth.GetID of the file /api/v1/tokens of the component API Token Management. Performing a manipulation results in privileges management. This vulnerability is cataloged as CVE-2026-68581. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in go-vikunja vikunja up to 2.3.0. It has been classified as critical. This affects the function web.Auth.GetID of the file /api/v1/tokens of the component API Token Management. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-68581 since 07/31/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 2.4.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51991). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• go-vikunja

Name

• vikunja

Version

• 2.0
• 2.1
• 2.2
• 2.3.0

Website

• Product: https://github.com/go-vikunja/vikunja/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion