CVE-2026-45757: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Rocket.Chat versions prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12 allow users deactivated for idleness to continue using previously issued login tokens. This insufficient session expiration issue enables inactive users to access authenticated REST endpoints despite administrative deactivation. The vulnerability is classified under CWE-613 and has a low CVSS score of 2.3. Fixes have been released in the specified versions.
AI Analysis
Technical Summary
CVE-2026-45757 describes an insufficient session expiration vulnerability in Rocket.Chat where users marked inactive by administrators using the users.deactivateIdle function can still use their existing login tokens to access authenticated REST endpoints. This issue affects versions prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. The vulnerability allows continued access despite user deactivation, potentially undermining session management controls. The vulnerability is fixed in the listed versions.
Potential Impact
Users who have been administratively deactivated for inactivity can continue to access authenticated REST endpoints using previously issued login tokens. This could allow unauthorized access by users who should no longer have active sessions. The impact is limited by the low CVSS score and the requirement for prior user inactivity deactivation.
Mitigation Recommendations
This vulnerability is fixed in Rocket.Chat versions 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. Users and administrators should upgrade to one of these fixed versions to remediate the issue. No additional mitigation guidance is provided or necessary beyond applying these official fixes.
CVE-2026-45757: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Description
Rocket.Chat versions prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12 allow users deactivated for idleness to continue using previously issued login tokens. This insufficient session expiration issue enables inactive users to access authenticated REST endpoints despite administrative deactivation. The vulnerability is classified under CWE-613 and has a low CVSS score of 2.3. Fixes have been released in the specified versions.
CVSS v4.0
Score 2.3low
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45757 describes an insufficient session expiration vulnerability in Rocket.Chat where users marked inactive by administrators using the users.deactivateIdle function can still use their existing login tokens to access authenticated REST endpoints. This issue affects versions prior to 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. The vulnerability allows continued access despite user deactivation, potentially undermining session management controls. The vulnerability is fixed in the listed versions.
Potential Impact
Users who have been administratively deactivated for inactivity can continue to access authenticated REST endpoints using previously issued login tokens. This could allow unauthorized access by users who should no longer have active sessions. The impact is limited by the low CVSS score and the requirement for prior user inactivity deactivation.
Mitigation Recommendations
This vulnerability is fixed in Rocket.Chat versions 8.5.0, 8.4.2, 8.3.4, 8.2.4, 8.1.5, 8.0.6, 7.13.8, and 7.10.12. Users and administrators should upgrade to one of these fixed versions to remediate the issue. No additional mitigation guidance is provided or necessary beyond applying these official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T06:54:34.221Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c4ce24853345fc1df8d60
Added to database: 06/24/2026, 21:32:18 UTC
Last enriched: 06/24/2026, 21:47:06 UTC
Last updated: 06/24/2026, 21:47:06 UTC
Views: 2
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.