Vulnerability in Go-Vikunja Vikunja
CVE-2026-111917
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.
Published .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/go-vikunja/vikunja/security/advisories/GHSA-4hv6-xc92-j86g (vendor-advisory)
- www.vulncheck.com/advisories/vikunja-2.3.0-before-2.7.0-websocket-authenticatio… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-111917?
- CVE-2026-111917 is a medium-severity vulnerability in Go-Vikunja Vikunja, classified under Insufficient Session Expiration. CVSS score: 6.5/10. Published 2026-10-17.
- How severe is CVE-2026-111917?
- Medium severity. CVSS v3 base score is 6.5 out of 10.