go-vikunja up to 2.3.0 Task Collection Endpoint tasks authorization

Summaryinfo

A vulnerability classified as problematic has been found in go-vikunja vikunja up to 2.3.0. This affects an unknown function of the file /api/v1/projects/{project}/views/{view}/tasks of the component Task Collection Endpoint. The manipulation leads to authorization. This vulnerability is traded as CVE-2026-68582. 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 and classified as problematic. This issue affects some unknown processing of the file /api/v1/projects/{project}/views/{view}/tasks of the component Task Collection Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality. The summary by CVE is:

Vikunja versions >= 0.24.0 and <= 2.3.0 contain a broken object level authorization (BOLA) vulnerability in the task-collection endpoint (GET /api/v1/projects/{project}/views/{view}/tasks). The endpoint loads the requested project view from the URL path without verifying the caller is authorized for it. For a link-share token holder, the task scope is pinned to the share's own project, but the view is taken from the attacker-controlled path and never re-validated. As a result, a holder of any project share link can read any other tenant's kanban bucket records — bucket titles and the full created_by user object (username, name, id) — for every view in the instance. The same missing pre-authorization view load also creates a project/view-ID existence oracle (404 vs. non-404) usable by link shares and ordinary authenticated users. Task contents remain constrained to the share's own project and are not disclosed. Fixed in 2.4.0.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-68582 since 07/31/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.4.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51992). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion