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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.1 | High | 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 | 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