CVE-2026-111917 go-vikunja CVE debrief

Who should care

Defenders responsible for Vikunja installations, especially those using WebSocket connections for real-time updates, should assess their exposure to this vulnerability and prioritize verification and remediation efforts.

Why it matters

CVE-2026-111917 is a high-severity vulnerability in Vikunja that allows attackers to maintain WebSocket access after session revocation. Defenders responsible for Vikunja installations should assess their exposure and prioritize verification and remediation efforts.

• Continued access to notification pushes, including comment, task, and project content, after session revocation.
• Potential for unauthorized access to sensitive information through WebSocket connections.
• Need for verification of affected versions and exposure to this vulnerability.
• Priority for updating to a fixed version or implementing compensating controls.

Technical summary

The CVE-2026-111917 vulnerability is caused by an improper session validation issue in Vikunja versions 2.3.0 before 2.7.0. The handleAuth function does not check the JWT sid claim against the sessions table, allowing attackers to maintain WebSocket access after session revocation or TOTP enrollment. This vulnerability allows attackers holding a stolen access token to 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. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using Vikunja for project

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using Vikunja for project management.

Recommended defensive actions

• Verify the version of Vikunja being used and assess exposure to this vulnerability.
• Review and update session validation and revocation procedures for WebSocket connections.
• Monitor for any suspicious WebSocket activity or unauthorized access attempts.
• Consider implementing additional security measures, such as token blacklisting or revocation lists.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but additional information from the vendor and other sources is limited. The vulnerability is described as an improper session validation issue that allows attackers to keep WebSocket access after revocation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.