High · CVSS 7.1CVE-2026-111917

Vikunja 2.3.0 before 2.7.0 WebSocket Authentication Ignores Session RevocationCVE-2026-111917

Answer in brief

CVE-2026-111917 records a High severity (CVSS 7.1) vulnerability in Vikunja 2.3.0 before 2.7.0 WebSocket Authentication Ignores Session Revocation. The current sources do not mark it as known exploited. The current feed maps go-vikunja/vikunja (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 17, 2026Updated Oct 17, 2026Source checked Oct 17, 2026First seen by HOL Oct 17, 2026Material review Oct 17, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps go-vikunja/vikunja (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
go-vikunja/vikunjageneric	>=2.3.0 <2.7.0	2.7.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for go-vikunja/vikunja.
Review the reported fix. Update go-vikunja/vikunja to 2.7.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 17, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.