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.

CVSS 3.1

8.3CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

0.3% chance of exploitation in the next 30 days; higher than 21% of CVEs (scores of 2026-10-26)

CWE

CWE-269

Published

2026-04-10

Modified

2026-10-26

Record from

the NVD, synced 2026-10-26

Affected

• vikunja:vikunja

Packages (OSV)

References

• https://github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d38226069722827
• https://github.com/go-vikunja/vikunja/pull/2583
• https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0
• https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72

Check your stackJSON