Vikunja 2.3.0 before 2.7.0 WebSocket Authentication Ignores Session Revocation
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.
CVE-2026-111917
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-111917
vikunja
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "go-vikunja",
"product": "vikunja",
"versions": [
{
"status": "affected",
"version": "2.3.0",
"lessThan": "2.7.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.7.0",
"versionType": "semver"
}
],
"packageURL": "pkg:golang/code.vikunja.io/api",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-111917
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #38913 · Revision 1
- Added to Heist Feed
- Publisher date