CVE-2026-55066 json
Vikunja: Cross-tenant IDOR in kanban move-task endpoint via unauthorized body task_id
published 2026-08-28 2 mo ago modified 2026-09-09 1 mo ago also EUVD-2026-67833 , GHSA-5pg6-m483-7vrg , GO-2026-6308
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- 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}/tasks accepts a body supplied task_id but TaskBucket.CanUpdate in pkg/models/kanban_task_bucket.go authorizes only the project, view, and bucket from the URL. updateTaskBucket then calls Task.ReadOne without a separate task permission check, returns the victim task contents, and can update the task done state when the attacker chooses a done bucket. Because task identifiers are global sequential values, an authenticated user can enumerate cross-tenant tasks and modify their completion metadata through both the v1 and v2 routes that share this model. 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@36cdc2c commit
- github.com/go-vikunja/vikunja#3239 pull request
- github.com/go-vikunja/vikunja/releases/tag/v2.4.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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/36cdc2ce2be0b8ccc74227d178b92047d59cd65f
web
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-5pg6-m483-7vrg
web, advisory
-
github.com
/go-vikunja/vikunja/releases/tag/v2.4.0
web
-
github.com
/go-vikunja/vikunja
package
Sources
- CVE List CVE-2026-55066
- GitHub Advisory GHSA-5pg6-m483-7vrg
- NVD CVE-2026-55066
- OSV GO-2026-6308
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.