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.
How to fix
- vikunja vikunja2.3.0 or later
- code.vikunja.io/api2.3.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| vikunja vikunja | v < 2.3.0 | 2.3.0 |
| code.vikunja.io/apiGo | v < 2.3.0, No range specified | 2.3.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.