Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-1054

NIXPKGS-2026-1054
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
updated 2 weeks, 4 days ago 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.

Affected products

vikunja
  • ==< 2.3.0

Matching in nixpkgs

pkgs.vikunja

Todo-app to organize your life

Ignored packages (1)

Package maintainers