Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vikunja | Vikunja | < 2.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d382260697Patch
- https://github.com/go-vikunja/vikunja/pull/2583Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72ExploitVendor Advisory
FAQ
What is CVE-2026-35595?
CVE-2026-35595 is a vulnerability with a CVSS score of 8.3 (HIGH). 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 c...
How severe is CVE-2026-35595?
CVE-2026-35595 has been rated HIGH with a CVSS base score of 8.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-35595?
Check the references section above for vendor advisories and patch information. Affected products include: Vikunja Vikunja.