CVE-2026-35595
Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the CanUpdate check at pkg/models/project_permissions.go:139-148 only requires CanWrite on the new parent project when changing parent_project_id. However, Vikunja's permission model uses a recursive CTE that walks up the project hierarchy to compute permissions. Moving a project under a different parent changes the permission inheritance chain. When a user has inherited Write access (from a parent project share) and reparents the child project under their own project tree, the CTE resolves their ownership of the new parent as Admin (permission level 2) on the moved project. This vulnerability is fixed in 2.3.0.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
code.vikunja.io/apiGo | < 2.3.0 | 2.3.0 |
Affected products
2Patches
Vulnerability mechanics
References
6- github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d38226069722827nvdPatchWEB
- github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72nvdExploitVendor AdvisoryWEB
- github.com/advisories/GHSA-2vq4-854f-5c72ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-35595ghsaADVISORY
- github.com/go-vikunja/vikunja/pull/2583nvdIssue TrackingWEB
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0nvdRelease NotesWEB
News mentions
0No linked articles in our index yet.