Privilege escalation in Go-Vikunja Vikunja
CVE-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 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.
Vulnerability class: Privilege Escalation
EPSS: 0.003 (21.2th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.3 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
Affected products
- Go-vikunja Vikunja — versions < 2.3.0
- Vikunja
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
- security-advisories@github.com (x_refsource_MISC, Issue Tracking)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (x_refsource_MISC, Release Notes)
Frequently asked questions
- What is CVE-2026-35595?
- CVE-2026-35595 is a high-severity vulnerability in Go-Vikunja Vikunja, classified under Improper Privilege Management. CVSS score: 8.3/10. Published 2026-04-10.
- How severe is CVE-2026-35595?
- High severity. CVSS v3 base score is 8.3 out of 10.