CVE 8.3 HIGH

Vikunja Affected by Privilege Escalation via Project Reparenting_CVE-2026-35595

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

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.

Basic Information

ID CVE-2026-35595
Source GitHub_M
Published Apr 10, 2026 at 15:58
Modified Apr 10, 2026 at 18:16

Affected Product

Vendor go-vikunja
Product vikunja
Version < 2.3.0
Affected Versions go-vikunja vikunja < 2.3.0

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.