# CVE-2026-68582: Vikunja 0.24.0 Broken Object Level Authorization via Link-Share Token

> Link-share token holders can read other tenants' kanban bucket records and user details due to missing authorization checks on view loading.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-rj9j-8772-4h6c, GO-2026-6749

## What is CVE-2026-68582?

CVE-2026-68582 is a critical missing authorization vulnerability in go-vikunja vikunja, published on 2 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vikunja versions >= 0.24.0 and <= 2.3.0 contain a broken object level authorization (BOLA) vulnerability in the task-collection endpoint (GET /api/v1/projects/{project}/views/{view}/tasks). The endpoint loads the requested project view from the URL path without verifying the caller is authorized for it. For a link-share token holder, the task scope is pinned to the share's own project, but the view is taken from the attacker-controlled path and never re-validated. As a result, a holder of any project share link can read any other tenant's kanban bucket records — bucket titles and the full created_by user object (username, name, id) — for every view in the instance. The same missing pre-authorization view load also creates a project/view-ID existence oracle (404 vs. non-404) usable by link shares and ordinary authenticated users. Task contents remain constrained to the share's own project and are not disclosed. Fixed in 2.4.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-68582?

3 open source packages ship an affected version, including code.vikunja.io/api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | From 0.24.0 | None |
| `code.vikunja.io/api` | Go | From 0.24.0 | 2.4.0 |
| `code.vikunja.io/api` | Go | From 0.24.0 | 2.4.0 |

## How do I fix CVE-2026-68582?

Upgrade code.vikunja.io/api to 2.4.0 or later.

## Is CVE-2026-68582 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68582 exists.

Public exploit code:

- PoC for CVE-2026-68582 / GHSA-rj9j-8772-4h6c — Vikunja link-share BOLA (github_poc): https://github.com/comradezephyr/CVE-2026-68582-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68582 and fix it if it is affected.

What it is: CVE-2026-68582 is a critical missing authorization vulnerability in go-vikunja vikunja, published on 2 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68582 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected from 0.24.0; no fix listed
- code.vikunja.io/api (Go): affected from 0.24.0; fixed in 2.4.0
- code.vikunja.io/api (Go): affected from 0.24.0; fixed in 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68582/ (Markdown: https://insights.sbomify.com/CVE-2026-68582/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68582
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68582
- OSV: https://osv.dev/vulnerability/CVE-2026-68582

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68582/
Summaries are generated and may contain mistakes; the official description above is the record.