CVE-2026-55065 json
Vikunja: Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api
published 2026-08-28 2 mo ago modified 2026-09-09 1 mo ago also GHSA-gg93-x632-9ccv , GO-2026-6313 , EUVD-2026-67832
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.
Patch / fix
- go code.vikunja.io/api 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@6895a77 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.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-gg93-x632-9ccv referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.vikunja.io/api | >=0.24.6, <2.4.0 >=0.24.6 |
2.4.0 |
Affected products
- go-vikunja vikunja
Classification
References
-
github.com
/go-vikunja/vikunja/pull/3239
web
-
github.com
/go-vikunja/vikunja/commit/6895a7765ef1667be4b79df29549d33b9e1ca9ca
web
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-gg93-x632-9ccv
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-55065
- GitHub Advisory GHSA-gg93-x632-9ccv
- NVD CVE-2026-55065
- OSV GO-2026-6313
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.