CVE-2026-35595
published 2026-04-10CVE-2026-35595: 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…
PriorityP352high8.3CVSS 3.1
AVNACLPRLUINSUCHIHAL
EPSS
0.29%
20.7th percentile
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
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| code.vikunja.io | api | >= 0 < 2.3.0 | 2.3.0 |
| go-vikunja | vikunja | < 2.3.0 | 2.3.0 |
| vikunja | vikunja | < 2.3.0 | 2.3.0 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Vikunja vulnerable to Privilege Escalation via Project Reparenting
ghsa·2026-04-10
CVE-2026-35595 [HIGH] CWE-269 Vikunja vulnerable to Privilege Escalation via Project Reparenting
Vikunja vulnerable to Privilege Escalation via Project Reparenting
## Summary
A user with Write-level access to a project can escalate their permissions to Admin by moving the project under a project they own. After reparenting, the recursive permission CTE resolves ownership of the new parent as Admin on the moved project. The attacker can then delete the project, manage shares, and remove other users' access.
## Details
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 h
VulDB
go-vikunja up to 2.2.x project_permissions.go privileges management (GHSA-2vq4-854f-5c72)
vuldb·2026-04-10·CVSS 8.3
CVE-2026-35595 [HIGH] go-vikunja up to 2.2.x project_permissions.go privileges management (GHSA-2vq4-854f-5c72)
A vulnerability was found in go-vikunja vikunja up to 2.2.x. It has been rated as critical. Impacted is an unknown function of the file pkg/models/project_permissions.go. The manipulation leads to improper privilege management.
This vulnerability is uniquely identified as CVE-2026-35595. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-04-10
Published