CVE-2026-35594: CWE-613: Insufficient Session Expiration in go-vikunja vikunja
Vikunja versions prior to 2. 3. 0 have an insufficient session expiration vulnerability in their link share authentication mechanism. The system constructs authorization objects solely from JWT claims without server-side validation, allowing previously issued JWTs to retain original permissions for up to 72 hours even after link shares are deleted or permissions downgraded. This issue is fixed in version 2. 3. 0. The vulnerability has a medium severity rating with a CVSS score of 6. 5.
AI Analysis
Technical Summary
CVE-2026-35594 describes an insufficient session expiration vulnerability (CWE-613) in the open-source task management platform Vikunja before version 2.3.0. The link share authentication function (GetLinkShareFromClaims) relies entirely on JWT claims without validating against the server-side database. Consequently, when a project owner deletes a link share or reduces its permissions, JWTs issued prior to that change continue to grant the original access level for the duration of the JWT's TTL (default 72 hours). This flaw allows stale tokens to maintain elevated permissions temporarily. The vulnerability is addressed in Vikunja 2.3.0.
Potential Impact
An attacker or user holding a previously issued JWT token can retain access permissions that should have been revoked due to link share deletion or permission downgrade for up to 72 hours. This could lead to unauthorized access or modification of project data during that window. The impact is limited to the duration of the JWT's time-to-live and does not allow permanent privilege escalation. The CVSS score of 6.5 reflects a medium severity with network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Vikunja to version 2.3.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 2.3.0, applying this official fix is the recommended remediation. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated but the fix is included in the new version release.
CVE-2026-35594: CWE-613: Insufficient Session Expiration in go-vikunja vikunja
Description
Vikunja versions prior to 2. 3. 0 have an insufficient session expiration vulnerability in their link share authentication mechanism. The system constructs authorization objects solely from JWT claims without server-side validation, allowing previously issued JWTs to retain original permissions for up to 72 hours even after link shares are deleted or permissions downgraded. This issue is fixed in version 2. 3. 0. The vulnerability has a medium severity rating with a CVSS score of 6. 5.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35594 describes an insufficient session expiration vulnerability (CWE-613) in the open-source task management platform Vikunja before version 2.3.0. The link share authentication function (GetLinkShareFromClaims) relies entirely on JWT claims without validating against the server-side database. Consequently, when a project owner deletes a link share or reduces its permissions, JWTs issued prior to that change continue to grant the original access level for the duration of the JWT's TTL (default 72 hours). This flaw allows stale tokens to maintain elevated permissions temporarily. The vulnerability is addressed in Vikunja 2.3.0.
Potential Impact
An attacker or user holding a previously issued JWT token can retain access permissions that should have been revoked due to link share deletion or permission downgrade for up to 72 hours. This could lead to unauthorized access or modification of project data during that window. The impact is limited to the duration of the JWT's time-to-live and does not allow permanent privilege escalation. The CVSS score of 6.5 reflects a medium severity with network attack vector, low attack complexity, no privileges required, no user interaction, and limited confidentiality and integrity impact.
Mitigation Recommendations
Upgrade Vikunja to version 2.3.0 or later, where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 2.3.0, applying this official fix is the recommended remediation. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated but the fix is included in the new version release.
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/10/2026, 4:21:05 PM
Last updated: 4/10/2026, 5:33:36 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.