High severity · published Apr 10, 2026
CVE-2026-35595
Vikunja Affected by Privilege Escalation via Project Reparenting
8.3
CVSS
0.3%
EPSS
No
On KEV
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 vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 21% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
VI
vikunja · go-vikunja
< 2.3.0 · source: vendor, NVD
Affected product
VI
vikunja
go-vikunja
More from vikunja
9.8
CVE-2026-28268
Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse
9.6
CVE-2026-33334
Vikunja Desktop: Any frontend XSS escalates to Remote Code Execution due to nodeIntegration
9.1
CVE-2026-34727
Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path
9.1
CVE-2026-27575
Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change
8.8
CVE-2026-33336
Vikunja Desktop vulnerable to Remote Code Execution via same-window navigation