# Vikunja: WebSocket authentication ignores server-side session state, so revoked sessions keep receiving live pushes

Advisory record · `GHSA-4hv6-xc92-j86g`

- **Identifiers:** `GHSA-4hv6-xc92-j86g` · `CVE-2026-111917` · `GO-2026-6715`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 9 Oct 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Oct 2026, 20:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code.vikunja.io/api` (Go): affected `>=2.3.0, <2.7.0`; fixed in `2.7.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vikunja (code.vikunja.io/api) versions 2.3.0 up to but not including 2.7.0 are affected. The WebSocket endpoint accepts any valid user JWT without checking its session against server-side session records, so a session revoked through the API keeps receiving live pushes, including notification content, and new connections can authenticate with a revoked token. An attacker needs a valid access token for the user, such as one stolen or leaked. Upgrade to version 2.7.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 29th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4hv6-xc92-j86g)

## Sources

- [GitHub Advisory Database: GHSA-4hv6-xc92-j86g](https://github.com/advisories/GHSA-4hv6-xc92-j86g)
- [OSV: GHSA-4hv6-xc92-j86g](https://osv.dev/vulnerability/GHSA-4hv6-xc92-j86g)
- <https://github.com/go-vikunja/vikunja/security/advisories/GHSA-4hv6-xc92-j86g>
- <https://github.com/go-vikunja/vikunja/commit/46ae98355462acbea451356326146675d3feeaab>
- <https://github.com/go-vikunja/vikunja>
- <https://github.com/go-vikunja/vikunja/releases/tag/v2.7.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4hv6-xc92-j86g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4hv6-xc92-j86g/>. Everything for agents: <https://agentprime.io/llms.txt>.