CVE-2026-55067 Vikunja: Authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-assignment
Authenticated users can move buckets to other tenants' views via mass assignment, enabling cross-tenant defacement in Vikunja.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-55067?
CVE-2026-55067 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Vikunja is an open-source self-hosted task management platform. Prior to 2.4.0, POST /api/v1/projects/{project}/views/{view}/buckets/{bucket} allows the request body project_view_id value to be mass assigned by Bucket.Update in pkg/models/kanban.go. The permission check validates that the bucket currently belongs to the URL project and view but does not validate the body selected destination view, allowing any authenticated user to relocate an attacker-owned bucket into another tenant’s Kanban view. The injected bucket retains attacker-controlled content and ownership, enabling cross-tenant defacement. This issue is fixed in version 2.4.0.
Weakness: CWE-639
Which versions are affected by CVE-2026-55067?
3 open source packages ship an affected version, including code.vikunja.io/api.
| Package | Affected | Fixed in |
|---|---|---|
code.vikunja.io/api Go | All versions | None |
code.vikunja.io/api Go | All versions | 2.4.0 |
code.vikunja.io/api Go | All versions | 2.4.0 |
How do I fix CVE-2026-55067?
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-55067 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55067 exists.
Sources
Also known as GHSA-569v-q83c-3j3g, GO-2026-6307.