CVE-2026-68582 Vikunja 0.24.0 Broken Object Level Authorization via Link-Share Token
Link-share token holders can read other tenants' kanban bucket records and user details due to missing authorization checks on view loading.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-68582?
CVE-2026-68582 is a critical missing authorization vulnerability in go-vikunja vikunja, published on 2 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-639
Which versions are affected by CVE-2026-68582?
3 open source packages ship an affected version, including code.vikunja.io/api.
| Package | Affected | Fixed in |
|---|---|---|
code.vikunja.io/api Go | From 0.24.0 | None |
code.vikunja.io/api Go | From 0.24.0 | 2.4.0 |
code.vikunja.io/api Go | From 0.24.0 | 2.4.0 |
How do I fix CVE-2026-68582?
Upgrade code.vikunja.io/api to 2.4.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-68582 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68582 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-rj9j-8772-4h6c, GO-2026-6749.