[ CVE-2026-68582 · Published 2 Aug 2026 ]
Vikunja: Link-share token reads any tenant's kanban buckets and enumerates usernames/IDs instance-wide (BOLA)
[ Why it matters ]Priority signals
- Public proof-of-concept exploit exists (CISA SSVC)
[ Description ]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.
[ Fixes ]Fixes and patches
- code.vikunja.io/api 2.4.0Fixed version · GitHub Advisories · go package code.vikunja.io/api: upgrade to 2.4.0 or later (affected >= 0.24.0, <= 2.3.0)
[ Packages ]Affected open-source packages
- code.vikunja.io/api goAffected >= 0.24.0, <= 2.3.0 · fixed in 2.4.0 · GHSA-rj9j-8772-4h6c