Untriaged
Permalink
CVE-2026-33676
6.5 MEDIUM
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Network (N)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): None (N)
- Availability (A): None (N)
- Modified Attack Vector (MAV): Network (N)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): None (N)
- Modified Availability (MA): None (N)
Activity log
- Created suggestion
Vikunja has Cross-Project Information Disclosure via Task Relations — Missing Authorization Check on Related Task Read
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.
References
-
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8cmm-j6c4-rr8v x_refsource_CONFIRMexploit
-
https://github.com/go-vikunja/vikunja/pull/2449 x_refsource_MISC
-
https://vikunja.io/changelog/vikunja-v2.2.2-was-released x_refsource_MISC
Affected products
vikunja
- ==< 2.2.1
Package maintainers
-
@leona-ya Leona Maroni <nix@leona.is>
-
@adamcstephens Adam C. Stephens <happy.plan4249@valkor.net>