CVE-2026-49277

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

State: Published
Severity: 2.3 Low
Published: Jun 24, 2026
Updated: Jun 26, 2026
Reserved: May 28, 2026

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.

Scores

CVSS	Score	Vector	Source
4.0	2.3 Low	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	GitHub_M

Weaknesses

CWE-613 Insufficient Session Expiration

Affected Products

Product	Versions
Rocket.ChatRocketChat	>= 8.5.0-rc.0, < 8.5.0Affected >= 8.4.0-rc.0, < 8.4.2Affected >= 8.3.0-rc.0, < 8.3.4Affected >= 8.2.0-rc.0, < 8.2.4Affected >= 8.1.0-rc.0, < 8.1.5Affected >= 8.0.0-rc.0, < 8.0.6Affected >= 7.11.0-rc.0, < 7.13.8Affected < 7.10.12Affected

References

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

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.