Skip to main content

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

0
High
Published: 10/17/2026 (10/17/2026, 21:31:19 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

Vikunja versions from 0.22.0 up to but not including 2.7.0 have a vulnerability where removed collaborators continue to receive project data via webhooks they created. This improper access revocation allows former collaborators to access task titles and descriptions, including new content created after their access was revoked.

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
>=0.22.0 <2.7.0
github.com/go-vikunja/vikunja
pkg:golang/github.com/go-vikunja/vikunja
Affected versions
>=0.22.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:24 UTC

Technical Analysis

CVE-2026-111919 describes an insufficient session expiration vulnerability in Vikunja, a project management tool. Specifically, collaborators who have been removed from a project can still receive updates through webhooks they previously created. This flaw allows unauthorized access to project data such as task titles and descriptions even after access revocation, due to improper invalidation of webhook sessions or tokens. The affected versions are from 0.22.0 up to but not including 2.7.0.

Potential Impact

Unauthorized former collaborators can continue to receive sensitive project information via webhooks, including task titles and descriptions created after their removal. This leads to a confidentiality breach of project data.

Mitigation Recommendations

No explicit patch or remediation details are provided in the input data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is applied, consider disabling or rotating webhooks created by collaborators who have been removed to prevent continued data leakage.

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.463Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ad3c6d42cdf04f656520819

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

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

Last updated: 10/17/2026, 22:21:02 UTC

Views: 12

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