go-vikunja up to 2.2.x project_permissions.go privileges management

Summaryinfo

A vulnerability categorized as critical has been discovered in go-vikunja vikunja up to 2.2.x. The affected element is an unknown function of the file pkg/models/project_permissions.go. The manipulation results in privileges management. This vulnerability was named CVE-2026-35595. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in go-vikunja vikunja up to 2.2.x. Affected is an unknown functionality of the file pkg/models/project_permissions.go. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-35595 since 04/03/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1068.

Upgrading to version 2.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch c03d682f48aff890eeb3c8b41d38226069722827 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• go-vikunja

Name

• vikunja

Version

• 2.0
• 2.1
• 2.2

License

• open-source

Website

• Product: https://github.com/go-vikunja/vikunja/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion