CVE-2026-111917 Vikunja 2.3.0 before 2.7.0 WebSocket Authentication Ignores Session Revocation
Attackers with stolen tokens maintain WebSocket access after session revocation, continuing to receive private task and project notifications.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-111917?
CVE-2026-111917 is a high-severity authentication bypass 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 2.3.0 before 2.7.0 contains an improper session validation vulnerability that allows attackers to keep WebSocket access after revocation because handleAuth never checks the JWT sid claim against the sessions table. Attackers holding a stolen access token can open or maintain connections to /api/v2/ws after session deletion or TOTP enrollment, continuing to receive the victim's notification.created pushes, including comment, task and project content.
Weakness: CWE-613
Which versions are affected by CVE-2026-111917?
3 open source packages ship an affected version, including code.vikunja.io/api.
| Package | Affected | Fixed in |
|---|---|---|
code.vikunja.io/api Go | All versions | None |
code.vikunja.io/api Go | From 2.3.0 | 2.7.0 |
code.vikunja.io/api Go | From 2.3.0 | 2.7.0 |
How do I fix CVE-2026-111917?
Upgrade code.vikunja.io/api to 2.7.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-111917 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111917 exists.
Sources
Also known as GHSA-355w-rx9g-pww7, GHSA-4hv6-xc92-j86g, GO-2026-6715.