Skip to main content

CVE-2026-111917: Insufficient Session Expiration in go-vikunja vikunja

0
High
VulnerabilityCVE-2026-111917cvecve-2026-111917
Published: 10/17/2026 (10/17/2026, 18:46:32 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

Vikunja versions 2.3.0 up to but not including 2.7.0 have a session validation vulnerability where WebSocket access remains active after session revocation. This occurs because the handleAuth function does not verify the JWT sid claim against the sessions table. An attacker with a stolen access token can maintain or open WebSocket connections to /api/v2/ws even after the session is deleted or TOTP enrollment is performed, allowing continued receipt of notifications including comments, tasks, and project content.

CVSS v4.0

Score 7.1high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

go-vikunja

vikunja

Affected versions
>=2.3.0 <2.7.0
github.com/go-vikunja/vikunja
pkg:golang/github.com/go-vikunja/vikunja
Affected versions
>=2.3.0 <2.7.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/17/2026, 19:18:28 UTC

Technical Analysis

CVE-2026-111917 describes an insufficient session expiration vulnerability in Vikunja versions >=2.3.0 and <2.7.0. The flaw lies in the handleAuth function, which fails to check the JWT sid claim against the sessions table, enabling attackers holding stolen access tokens to keep WebSocket connections alive after session revocation events such as session deletion or TOTP enrollment. This allows attackers to continue receiving victim notifications related to comments, tasks, and project content via the /api/v2/ws endpoint.

Potential Impact

Attackers with stolen access tokens can maintain unauthorized WebSocket connections after legitimate session revocation, potentially exposing victim notification data including comments, tasks, and project content. This undermines session termination controls and may lead to unauthorized data exposure.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-17T12:18:55.462Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad3c6d22cdf04f656520815

Added to database: 10/17/2026, 19:04:50 UTC

Last enriched: 10/17/2026, 19:18:28 UTC

Last updated: 10/17/2026, 19:19:31 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses