CVE-2026-49277 PUBLISHED

Rocket.Chat: OAuth access and refresh tokens remain valid after account deactivation

Assigner: GitHub_M
Reserved: 28.05.2026 Published: 24.06.2026 Updated: 24.06.2026

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.

Metrics

CVSS 4.0

CVSS Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CVSS Score: 2.3

Exploitability Metrics		Vulnerable System Impact Metrics		Subsequent System Impact Metrics
Attack Vector	Network	Confidentiality	Low	Confidentiality	None
Attack Complexity	High	Integrity	Low	Integrity	None
Attack Requirements	None	Availability	None	Availability	None
Privileges Required	None
User Interaction	Passive

CVSS 4.0

Product Status

Vendor	RocketChat
Product	Rocket.Chat
Versions	Version >= 8.5.0-rc.0, < 8.5.0 is affected Version >= 8.4.0-rc.0, < 8.4.2 is affected Version >= 8.3.0-rc.0, < 8.3.4 is affected Version >= 8.2.0-rc.0, < 8.2.4 is affected Version >= 8.1.0-rc.0, < 8.1.5 is affected Version >= 8.0.0-rc.0, < 8.0.6 is affected Version >= 7.11.0-rc.0, < 7.13.8 is affected Version < 7.10.12 is affected

References

https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-39hg-492f-3c4f

Problem Types

CWE-613: Insufficient Session Expiration CWE