CVE-2026-55067 json
Vikunja: Authenticated cross-tenant kanban-bucket relocation via `project_view_id` mass-assignment
published 2026-08-28 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-67834 , GHSA-569v-q83c-3j3g , GO-2026-6307
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go code.vikunja.io/api 2.4.0
- vikunja vikunja 2.4.0
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260902T191204-160000.1.1
suse advisories SUSE-SU-2026:23692-1SUSE-SU-2026:23712-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260902T191204-160000.1.1
opensuse advisories openSUSE-SU-2026:21812-1
- github.com/go-vikunja/vikunja@b31d606 commit
- github.com/go-vikunja/vikunja#3239 pull request
- github.com/go-vikunja/vikunja/releases/tag/v2.4.0 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-569v-q83c-3j3g referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.vikunja.io/api | <2.4.0 all versions |
2.4.0 |
Affected products
- go-vikunja vikunja
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/go-vikunja/vikunja/pull/3239
web
-
github.com
/go-vikunja/vikunja/commit/b31d606b8879ebe98fbb2ac5d8b3066b86f59868
web
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-569v-q83c-3j3g
exploit, web, advisory
-
github.com
/go-vikunja/vikunja/releases/tag/v2.4.0
web
-
github.com
/go-vikunja/vikunja
package
Sources
- CVE List CVE-2026-55067
- GitHub Advisory GHSA-569v-q83c-3j3g
- NVD CVE-2026-55067
- OSV GO-2026-6307
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.