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.
References
Configurations
No configuration.
History
03 Aug 2026, 20:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rj9j-8772-4h6c - |
02 Aug 2026, 13:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-08-02 13:16
Updated : 2026-08-03 20:17
NVD link : CVE-2026-68582
Mitre link : CVE-2026-68582
CVE.ORG link : CVE-2026-68582
JSON object : View
Products Affected
No product.
CWE
CWE-639
Authorization Bypass Through User-Controlled Key
