CVE-2026-49277: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Rocket.Chat 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 do not revoke OAuth bearer or refresh tokens when a user is deactivated. This allows a deactivated user to continue using existing OAuth access tokens and mint new access tokens from existing refresh tokens. The issue is addressed in the specified fixed versions.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-49277) in Rocket.Chat is due to insufficient session expiration (CWE-613). Specifically, prior to the fixed versions, the system fails to revoke OAuth bearer and refresh tokens upon user deactivation. Consequently, deactivated users retain the ability to use existing access tokens and generate new ones from refresh tokens, potentially allowing continued access despite deactivation. The vulnerability is fixed starting from 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.
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. This undermines the intended access control mechanism by allowing continued access after user deactivation. The CVSS score is low (2.3), reflecting limited impact and higher attack complexity.
Mitigation Recommendations
Upgrade Rocket.Chat to one of the fixed versions: 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, or 8.5.0. These versions revoke OAuth bearer and refresh tokens upon user deactivation, mitigating the vulnerability. Patch status is confirmed by the vendor advisory. No other specific mitigations are indicated.
CVE-2026-49277: CWE-613: Insufficient Session Expiration in RocketChat Rocket.Chat
Description
Rocket.Chat 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 do not revoke OAuth bearer or refresh tokens when a user is deactivated. This allows a deactivated user to continue using existing OAuth access tokens and mint new access tokens from existing refresh tokens. The issue is addressed in the specified fixed versions.
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 due to insufficient session expiration (CWE-613). Specifically, prior to the fixed versions, the system fails to revoke OAuth bearer and refresh tokens upon user deactivation. Consequently, deactivated users retain the ability to use existing access tokens and generate new ones from refresh tokens, potentially allowing continued access despite deactivation. The vulnerability is fixed starting from 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.
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. This undermines the intended access control mechanism by allowing continued access after user deactivation. The CVSS score is low (2.3), reflecting limited impact and higher attack complexity.
Mitigation Recommendations
Upgrade Rocket.Chat to one of the fixed versions: 7.10.12, 7.13.8, 8.0.6, 8.1.5, 8.2.4, 8.3.4, 8.4.2, or 8.5.0. These versions revoke OAuth bearer and refresh tokens upon user deactivation, mitigating the vulnerability. Patch status is confirmed by the vendor advisory. No other specific mitigations are indicated.
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: 06/24/2026, 21:46:53 UTC
Last updated: 06/24/2026, 21:46:53 UTC
Views: 3
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.