NIXPKGS-2026-1054
GitHub issue
published on
Permalink
CVE-2026-35595
8.3 HIGH
- CVSS version: 3.1
- Attack vector (AV): NETWORK
- Attack complexity (AC): LOW
- Privileges required (PR): LOW
- User interaction (UI): NONE
- Scope (S): UNCHANGED
- Confidentiality impact (C): HIGH
- Integrity impact (I): HIGH
- Availability impact (A): LOW
by @LeSuisse Activity log
- Created suggestion
- @LeSuisse ignored package vikunja-desktop
- @LeSuisse accepted
- @LeSuisse published on GitHub
Vikunja Affected by Privilege Escalation via Project Reparenting
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.
References
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854f-5c72 x_refsource_CONFIRM
-
https://github.com/go-vikunja/vikunja/pull/2583 x_refsource_MISC
Ignored references (1)
-
https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 x_refsource_MISC
Affected products
vikunja
- ==< 2.3.0
Matching in nixpkgs
Ignored packages (1)
pkgs.vikunja-desktop
Desktop App of the Vikunja to-do list app
Package maintainers
-
@leona-ya Leona Maroni <nix@leona.is>
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>