# CVE-2026-111919: Vikunja 0.22.0 before 2.7.0 Improper Access Revocation via Webhooks

> Removed collaborators can continue receiving sensitive project data via webhooks they created, exposing task details after access revocation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 19 Oct 2026
- **Also known as:** GHSA-276j-w3vx-r5jh, GHSA-hjx8-qv73-f7cm, GO-2026-6733

## What is CVE-2026-111919?

CVE-2026-111919 is a high-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.22.0 before 2.7.0 contains an improper access revocation vulnerability that allows removed collaborators to keep receiving project data through webhooks they created. Former collaborators keep receiving task titles and descriptions through their webhook, including content created after their access was revoked.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

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.22.0 | None |
| `code.vikunja.io/api` | Go | From 0.22.0 to 2.6.0 | None |
| `code.vikunja.io/api` | Go | From 0.22.0 to 2.6.0 | None |

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

No fix has been published for CVE-2026-111919 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111919 is a high-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-111919 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected from 0.22.0; no fix listed
- code.vikunja.io/api (Go): affected from 0.22.0 up to 2.6.0; no fix listed
- code.vikunja.io/api (Go): affected from 0.22.0 up to 2.6.0; no fix listed

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-111919/ (Markdown: https://insights.sbomify.com/CVE-2026-111919/index.md)
```

## Sources

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

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