Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-35594: CWE-613: Insufficient Session Expiration in go-vikunja vikunja

0
Medium
VulnerabilityCVE-2026-35594cvecve-2026-35594cwe-613
Published: Fri Apr 10 2026 (04/10/2026, 15:55:04 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's link share authentication (GetLinkShareFromClaims in pkg/models/link_sharing.go) constructs authorization objects entirely from JWT claims without any server-side database validation. When a project owner deletes a link share or downgrades its permissions, all previously issued JWTs continue to grant the original permission level for up to 72 hours (the default service.jwtttl). This vulnerability is fixed in 2.3.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/18/2026, 14:20:41 UTC

Technical Analysis

CVE-2026-35594 describes a vulnerability in the go-vikunja vikunja task management platform where the link share authentication (GetLinkShareFromClaims) relies entirely on JWT claims without validating against the server-side database. As a result, when a project owner deletes a link share or reduces its permissions, JWT tokens issued before the change remain valid with the original permissions for the duration of the JWT time-to-live (default 72 hours). This constitutes insufficient session expiration (CWE-613). The vulnerability is fixed in version 2.3.0.

Potential Impact

An attacker or user holding a previously issued JWT token can retain access rights that should have been revoked or reduced, potentially leading to unauthorized access to project resources for up to 72 hours after permission changes. The impact is limited to confidentiality and integrity with no direct availability impact. The CVSS score is 6.5 (medium severity).

Mitigation Recommendations

Upgrade to Vikunja version 2.3.0 or later, where this vulnerability is fixed. Since no official patch or workaround is detailed beyond the version update, applying this upgrade is the recommended remediation. Patch status is not explicitly stated beyond the fix in 2.3.0, so verify with the vendor advisory for the latest 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
GitHub_M
Date Reserved
2026-04-03T21:25:12.161Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69d91fde1cc7ad14dacba29a

Added to database: 4/10/2026, 4:05:50 PM

Last enriched: 4/18/2026, 2:20:41 PM

Last updated: 5/25/2026, 2:17:17 AM

Views: 64

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