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?
- Medium severity, with a CVSS score of 4, published 9 October 2026.
- Which products and versions are affected?
- code.vikunja.io/api (Go) ECOSYSTEM:introduced=0.9,fixed=2.6.0; Vikunja 0.9 through 2.5.0.
- Is there a fix for This vulnerability?
- Yes. code.vikunja.io/api (Go): upgrade to 2.6.0 or later. 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.
- Am I affected?
- Check whether you run code.vikunja.io/api (Go) or Vikunja 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
- code.vikunja.io/api (Go): upgrade to 2.6.0 or later
go get code.vikunja.io/api@v2.6.0
Technical details
The TaskRelation.CanDelete() authorization check in pkg/models/task_relation_permissions.go only verifies write access to the base task (TaskID) but fails to check read access to the related task (OtherTaskID), unlike the creation path. When a relation is deleted, both the forward and inverse relation rows are removed from the database, causing the relation to vanish from the far project as well. The vulnerability affects DELETE /api/v1/tasks/{id}/relations/{kind}/{otherTaskId} endpoints and requires the attacker to have write access to a task already related to an inaccessible task.
Affected products
- Vikunja Vikunja 0.9 through 2.5.0
Timeline
- 2026-10-09: disclosed
- 2026-10-09: patched: Version 2.6.0 released with fix via commit 077dc4de79ce6f1ab59215a2c7bf9b30423685f2