CVE-2026-35595 Vikunja Affected by Privilege Escalation via Project Reparenting
HighCVSS 8.3
EPSS 0.30%
- Published
- Updated
- Exploit status
- No public exploit known
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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| code.vikunja.io/api(Go) | < 2.3.0 | 2.3.0 |
| code.vikunja.io/api(Go) | All versions | No fix listed |
| go-vikunja vikunja | = < 2.3.0 | No fix listed |
| code.vikunja.io/api(Go) | <= 2.2.2 | No fix listed |
| vikunja | < 2.3.0 | 2.3.0 |
References
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72 exploit vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/go-vikunja/vikunja/pull/2583 issue-tracking patch
- https://github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d38226069722827 patch
- github.com product
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 release-notes
- github.com