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 TaskAssignee.ReadAll method in pkg/models/task_assignees.go returns user objects without blanking the Email field, disclosing assignee email addresses to any principal with task.CanRead permission. The vulnerability affects the GET /api/v1/tasks/{id}/assignees and /api/v2/tasks/{id}/assignees endpoints; other similar endpoints correctly obfuscate the email field, indicating this is an oversight rather than design. An authenticated read-only project member can query the endpoint to extract email addresses.
Affected products
- Vikunja API before 2.6.0
Identifiers
- GHSA-8wvg-r2j4-3737
- GO-2026-6723
Timeline
- 2026-08-31: disclosed
- 2026-08-31: patched: v2.6.0 released