CVE 2.3 LOW

Rocket.Chat: OAuth access and refresh tokens remain valid after account deactivation_CVE-2026-49277

2.3 / 10
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

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.

Basic Information

ID CVE-2026-49277
Source GitHub_M
Published Jun 24, 2026 at 21:04

Affected Product

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

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.