Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- code.vikunja.io/api (Go) SEMVER:introduced=0; Vikunja API before 2.6.0.
- Is there a fix for This vulnerability?
- Yes: fixed in 2.6.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run code.vikunja.io/api (Go) or Vikunja API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.6.0
Technical details
The vulnerability is a cross-project authorization bypass in the subtask expansion endpoint. When a task list is retrieved with the subtask expansion parameter (?expand[]=subtasks), the API applies access control filtering to the main task list but fails to apply the same filtering when recursively fetching linked subtasks from other projects. An authenticated user with low privilege access to one project can exploit this to read arbitrary task data (title, description, dates, assignees, labels, attachment metadata) from any private project containing a subtask linked under a task they can see.
Affected products
- Vikunja API before 2.6.0
Identifiers
- GHSA-3hc7-r24j-rpwc
- GO-2026-6714
Timeline
- 2026-08-31: disclosed
- 2026-10-19: advisory