CVE-2026-49277: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Rocket.Chat is an open-source, secure, fully customizable communications platform. 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, Rocket.Chat does not revoke OAuth bearer or refresh tokens when a user is deactivated. A deactivated user can continue using an existing OAuth access token, and can also mint a fresh access token from an existing refresh token. This vulnerability is fixed in 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.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-49277) in Rocket.Chat is an insufficient session expiration flaw (CWE-613) where OAuth bearer and refresh tokens are not revoked upon user deactivation. As a result, deactivated users retain access via existing tokens and can generate new access tokens from refresh tokens. The vulnerability affects multiple versions prior to 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, and 8.5.0, with fixes applied in these versions.
Potential Impact
Deactivated users can continue to access Rocket.Chat resources using existing OAuth access tokens and can mint new access tokens from refresh tokens, potentially allowing unauthorized access after account deactivation. The CVSS 4.0 score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
A fix is available in Rocket.Chat versions 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, and 8.5.0. Users should upgrade to these versions or later to ensure OAuth tokens are properly revoked upon user deactivation. No other mitigation guidance is provided or necessary.
CVE-2026-49277: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Description
Rocket.Chat is an open-source, secure, fully customizable communications platform. 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, Rocket.Chat does not revoke OAuth bearer or refresh tokens when a user is deactivated. A deactivated user can continue using an existing OAuth access token, and can also mint a fresh access token from an existing refresh token. This vulnerability is fixed in 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.
CVSS v4.0
Score 2.3low
Affected software
pkg:github/rocketchat/Rocket.ChatRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-49277) in Rocket.Chat is an insufficient session expiration flaw (CWE-613) where OAuth bearer and refresh tokens are not revoked upon user deactivation. As a result, deactivated users retain access via existing tokens and can generate new access tokens from refresh tokens. The vulnerability affects multiple versions prior to 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, and 8.5.0, with fixes applied in these versions.
Potential Impact
Deactivated users can continue to access Rocket.Chat resources using existing OAuth access tokens and can mint new access tokens from refresh tokens, potentially allowing unauthorized access after account deactivation. The CVSS 4.0 score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
A fix is available in Rocket.Chat versions 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, and 8.5.0. Users should upgrade to these versions or later to ensure OAuth tokens are properly revoked upon user deactivation. No other mitigation guidance is provided or necessary.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T20:07:58.861Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c4ce24853345fc1df8d69
Added to database: 06/24/2026, 21:32:18 UTC
Last enriched: 07/01/2026, 22:28:37 UTC
Last updated: 08/08/2026, 12:41:11 UTC
Views: 58
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.