Security Digest · Vulnerability record
CVE-2026-68582: Vikunja: Link-share token reads any tenant's kanban buckets and enumerates usernames/IDs instance-wide (BOLA)
Vikunja versions >= 0.24.0 and
CVSS 9.3 Critical EPSS 0.3% · p18
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.3%, percentile 18: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 18% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
code.vikunja.io/api(Go) >= 0.24.0, <= 2.3.0, fixed in 2.4.0. Check your lockfile, including transitive dependencies.
What it is
Vikunja versions >= 0.24.0 and
From the GitHub advisory
Summary
The task-collection endpoint GET /api/v1/projects/{project}/views/{view}/tasks loads the requested project view straight from the URL path without verifying the caller is authorized for it. For a link-share token, the task query is correctly pinned to the share's own project, but the view is taken from the attacker-controlled path and never re-validated against the share. A holder of a share link to any project can therefore point the endpoint at any other tenant's kanban view and receive that view's bucket records — bucket titles plus the full createdby user object (username, name, id) — for every view in the instance. The same missing pre-authorization view load also yields a project/view-ID existence oracle (404 vs. non-404) usable by link shares and ordinary authenticated users alike.
Details
Root cause is in TaskCollection.ReadAll (pkg/models/taskcollection.go).
1. The view is resolved from the URL params before any permission check:
Weakness type: CWE-639, CWE-863.
Product: code.vikunja.io/api (Go) · Assigned by: VulnCheck · Published: 2026-08-02
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | code.vikunja.io/api | >= 0.24.0, <= 2.3.0 | 2.4.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| go-vikunja | vikunja | 0.24.0 < 2.4.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| VulnCheck | 4.0 | 9.3 Critical | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| VulnCheck | 3.1 | 6.5 Medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.27% probability of exploitation activity in the next 30 days; percentile 18.
Timeline
- — CVE record published by VulnCheck
- — CVE record last updated
- — GitHub-reviewed advisory GHSA-rj9j-8772-4h6c published (critical)
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
Vulnerability records
- GitHub Advisory GHSA-rj9j-8772-4h6c github.com
- CVE.org record CVE-2026-68582 cve.org
- NVD entry CVE-2026-68582 nvd.nist.gov
Other references from the CVE record and advisory
- VulnCheck Advisory: Vikunja 0.24.0 Broken Object Level Authorization via Link-Share Token vulncheck.com
- github.com github.com