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; Go-Vikunja Api 0.9.0 to 2.5.0.
- Is there a fix for This vulnerability?
- Yes: fixed in 2.6.0. Until then: Restrict write access to projects containing tasks that are related to tasks in sensitive projects until upgrading. 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 Go-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
Restrict write access to projects containing tasks that are related to tasks in sensitive projects until upgrading.
Technical details
The TaskRelation.CanDelete() method in code.vikunja.io/api only checks write access on the base task (TaskID) but fails to verify read access on the linked task (OtherTaskID), unlike the CanCreate() method which properly enforces both. When a relation is deleted via DELETE /api/v1/tasks/{id}/relations/{kind}/{otherTaskId}, both the forward and inverse relation rows are removed, causing the link to disappear for all users, including those in the target project.
Affected products
- go-vikunja api 0.9.0 to 2.5.0
Identifiers
- GHSA-w2ch-4xgr-22ww
- GO-2026-6754
Timeline
- 2026-08-31: disclosed
- 2026-10-19: patched