Vikunja Affected by Privilege Escalation via Project Reparenting
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Privilege escalation
- Confidentiality · integrity · availability
- High · High · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-269.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| go-vikunja | vikunja | before 2.3.0 | 2.3.0 | Patch available | CNA |
| — | code.vikunja.io/api (Go) | before 2.3.0 | 2.3.0 | Patch available | GHSA-2vq4-854f-5c72 |
- vikunja Vendorgo-vikunja Affected before 2.3.0 Fixed in 2.3.0 Patch available CNA
- code.vikunja.io/api (Go) Vendor— Affected before 2.3.0 Fixed in 2.3.0 Patch available GHSA-2vq4-854f-5c72
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | before 2.3.0 | Vulnerable | go-vikunja |
- cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions before 2.3.0 Vulnerable ·go-vikunja
Remediation
- Fix · CNA vikunja (go-vikunja) Fixed in 2.3.0
- Fix · GHSA-2vq4-854f-5c72 code.vikunja.io/api (Go) Fixed in 2.3.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-35595
- 2026-10-03 Alias added: GHSA-2vq4-854f-5c72
References
More go-vikunja Vikunja vulnerabilities
- TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
- TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
- TI-2026-26060 Vikunja Vulnerable to Link Share Hash Disclosure via ReadAll Endpoint Enables Permission Escalation CVSS 3.1HIGH 7.5
- TI-2026-20965 Vikunja Affected by XSS Via Task Preview CVSS 4.0HIGH 8.6
- TI-2026-25727 Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement CVSS 3.1HIGH 8.1
- TI-2026-25726 Vikunja has a 2FA Bypass via Caldav Basic Auth CVSS 4.0MEDIUM 6.9
Sources
- CVE-2026-35595 · CVE Program
- CVE-2026-35595 · NVD
- FIRST EPSS
- GHSA-2vq4-854f-5c72 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences