CVE-2026-35595
This vulnerability is fixed in 2.3.0.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.29%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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 3.1
- 8.3 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- EPSS
- 0.29% probability · 22th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-269
- Affected
- vikunja/vikunja
- Source
- security-advisories@github.com
References
- https://github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d38226069722827Patch
- https://github.com/go-vikunja/vikunja/pull/2583Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72Exploit, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.