Is CVE-2026-111917 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-111917 being exploited in the wild.

How severe is CVE-2026-111917?

Medium severity, with a CVSS score of 6.5, published 17 October 2026.

Which products and versions are affected?

code.vikunja.io/api (Go) SEMVER:introduced=0; Vikunja 2.3.0 to 2.6.0.

Is there a fix for CVE-2026-111917?

Yes: fixed in 2.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-111917 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-111917?

Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-111917: Vikunja WebSocket session validation bypass

CVE-2026-111917 · Severity: medium · CVSS 6.5 · Published 2026-10-17

Vikunja is a task management and collaboration platform that uses WebSocket connections to deliver real-time notifications to users. Attackers with a stolen access token can maintain or reopen WebSocket connections even after the user has revoked the session—for example, after losing a device or enabling two-factor authentication—and continue receiving the victim's notifications, comments, tasks, and project information indefinitely.

Technologies: code.vikunja.io/api (Go), Vikunja. Vendors: Go, Vikunja.

Quick answers

Is CVE-2026-111917 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-111917 being exploited in the wild.
How severe is CVE-2026-111917?: Medium severity, with a CVSS score of 6.5, published 17 October 2026.
Which products and versions are affected?: code.vikunja.io/api (Go) SEMVER:introduced=0; Vikunja 2.3.0 to 2.6.0.
Is there a fix for CVE-2026-111917?: Yes: fixed in 2.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111917 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-111917?: Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.7.0

Technical details

The vulnerability is an improper session validation in the WebSocket authentication handler (handleAuth), which verifies JWT signature and token type but never validates the session ID (sid) claim against the server-side sessions table. A stolen or pre-revocation access token can authenticate new WebSocket connections after the legitimate session has been deleted via DELETE /api/v2/user/sessions/{id} or TOTP enrollment. Existing connections remain authenticated and continue receiving push events with no time bound until the attacker closes the connection.

Affected products

Vikunja Vikunja 2.3.0 to 2.6.0

Identifiers

CVE-2026-111917
GHSA-4hv6-xc92-j86g
GO-2026-6715

Timeline

2026-10-03: disclosed
2026-10-17: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.