CVE-2026-71206: CWE-613 Insufficient Session Expiration in go-shiori shiori
Shiori's CheckToken function (internal/domains/auth.go) validates only the JWT's HMAC signature and returns the embedded claims.Account object unmodified, never re-fetching the account from the database. No session store or token-revocation mechanism exists in the codebase. Deleting an account or demoting it from owner to a regular role has no effect on tokens already issued to that account — a deleted or demoted owner's token continues authenticating with its original owner-level privileges until natural expiry, which can be up to 30 days with 'remember me' enabled.
AI Analysis
Technical Summary
The vulnerability in go-shiori's Shiori application involves insufficient session expiration controls (CWE-613). The CheckToken function validates JWT tokens solely by their HMAC signature and returns embedded claims without verifying the current account status from the database. Consequently, tokens issued to accounts that have been deleted or had their privileges reduced continue to authenticate with their original privileges until the token naturally expires. There is no session store or token revocation mechanism implemented, allowing potentially unauthorized access for up to 30 days when 'remember me' is enabled.
Potential Impact
An attacker or user holding a valid JWT token can retain access with the original privileges even after the associated account is deleted or demoted. This can lead to unauthorized access with elevated privileges, compromising confidentiality and integrity of the system. The vulnerability has a high impact on confidentiality and integrity, with limited impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling the 'remember me' feature to reduce token lifetime or implement manual token revocation mechanisms if possible. Monitor for updates from the go-shiori project regarding an official fix.
CVE-2026-71206: CWE-613 Insufficient Session Expiration in go-shiori shiori
Description
Shiori's CheckToken function (internal/domains/auth.go) validates only the JWT's HMAC signature and returns the embedded claims.Account object unmodified, never re-fetching the account from the database. No session store or token-revocation mechanism exists in the codebase. Deleting an account or demoting it from owner to a regular role has no effect on tokens already issued to that account — a deleted or demoted owner's token continues authenticating with its original owner-level privileges until natural expiry, which can be up to 30 days with 'remember me' enabled.
CVSS v3.1
Score 8.2high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in go-shiori's Shiori application involves insufficient session expiration controls (CWE-613). The CheckToken function validates JWT tokens solely by their HMAC signature and returns embedded claims without verifying the current account status from the database. Consequently, tokens issued to accounts that have been deleted or had their privileges reduced continue to authenticate with their original privileges until the token naturally expires. There is no session store or token revocation mechanism implemented, allowing potentially unauthorized access for up to 30 days when 'remember me' is enabled.
Potential Impact
An attacker or user holding a valid JWT token can retain access with the original privileges even after the associated account is deleted or demoted. This can lead to unauthorized access with elevated privileges, compromising confidentiality and integrity of the system. The vulnerability has a high impact on confidentiality and integrity, with limited impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider disabling the 'remember me' feature to reduce token lifetime or implement manual token revocation mechanisms if possible. Monitor for updates from the go-shiori project regarding an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TuranSec
- Date Reserved
- 2026-08-05T06:56:15.799Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a72e5cbbf8831d539735249
Added to database: 08/05/2026, 07:27:07 UTC
Last enriched: 08/05/2026, 07:41:44 UTC
Last updated: 08/06/2026, 00:41:15 UTC
Views: 7
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.
External Links
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.