# CVE-2026-111921: Vikunja 0.13.0 before 2.7.0 Incorrect Authorization in Link Share Deletion

> Project members with Write permission can delete admin-tier link shares, revoking access and invalidating sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-92qc-qm37-9wr9, GHSA-fmmf-xq98-g327, GO-2026-6730

## What is CVE-2026-111921?

CVE-2026-111921 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vikunja 0.13.0 before 2.7.0 contains an incorrect authorization vulnerability that allows project members with Write permission to delete admin-tier link shares because the delete permission check reads an unloaded share object. Attackers can send DELETE requests to the v1 or v2 projects shares endpoints with sequential share IDs to revoke admin links and invalidate existing share sessions.

Weakness: CWE-863 (Incorrect Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | All versions | None |
| `code.vikunja.io/api` | Go | From 0.13.0 | 2.7.0 |
| `code.vikunja.io/api` | Go | From 0.13.0 | 2.7.0 |

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

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

## Is CVE-2026-111921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111921 is a medium-severity missing authorization vulnerability in go-vikunja vikunja, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111921 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected all versions; no fix listed
- code.vikunja.io/api (Go): affected from 0.13.0; fixed in 2.7.0
- code.vikunja.io/api (Go): affected from 0.13.0; fixed in 2.7.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-111921/ (Markdown: https://insights.sbomify.com/CVE-2026-111921/index.md)
```

## Sources

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

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