Summaryinfo

A vulnerability was found in go-vikunja vikunja up to 2.2.0. It has been rated as problematic. This issue affects some unknown processing of the component API. This manipulation of the argument related_tasks causes authorization. This vulnerability is tracked as CVE-2026-33676. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in go-vikunja vikunja up to 2.2.0. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component API. The manipulation of the argument related_tasks with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect confidentiality. The summary by CVE is:

Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, when the Vikunja API returns tasks, it populates the `related_tasks` field with full task objects for all related tasks without checking whether the requesting user has read permission on those tasks' projects. An authenticated user who can read a task that has cross-project relations will receive full details (title, description, due dates, priority, percent completion, project ID, etc.) of tasks in projects they have no access to. Version 2.2.1 patches the issue.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-33676 since 03/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2.2.1 eliminates this vulnerability. The upgrade is hosted for download at vikunja.io. Applying the patch 833f2aec006ac0f6643c41872e45dd79220b9174 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• go-vikunja

Name

• vikunja

Version

• 2.0
• 2.1
• 2.2.0

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

Discussion