CVE-2026-35595 Vikunja Affected by Privilege Escalation via Project Reparenting
Attackers can escalate privileges to Admin on projects by reparenting them under their own project tree due to flawed permission inheritance logic.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-35595?
CVE-2026-35595 is a high-severity vulnerability in go-vikunja vikunja, published on 10 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-269
Which versions are affected by CVE-2026-35595?
3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
code.vikunja.io/api Go | All versions | None |
code.vikunja.io/api Go | All versions | 2.3.0 |
code.vikunja.io/api Go | All versions | 2.3.0 |
Products include Vikunja Vikunja.
How do I fix CVE-2026-35595?
Upgrade code.vikunja.io/api to 2.3.0 or later.
Is CVE-2026-35595 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35595 exists.
Other vulnerabilities in go-vikunja vikunja
- CVE-2026-28268 Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
- CVE-2026-27575 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change
- CVE-2026-25935 Vikunja Affected by XSS Via Task Preview
- CVE-2026-33316 Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement
- CVE-2026-33678 Vikunja has IDOR in Task Attachment ReadOne Allows Cross-Project File Access and Deletion
Sources
Also known as GHSA-2vq4-854f-5c72, GO-2026-4952.