CVE-2026-49277 Rocket.Chat: OAuth access and refresh tokens remain valid after account deactivation
Deactivated users retain valid OAuth tokens, allowing continued access and token renewal, requiring an upgrade to Rocket.Chat.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-49277?
CVE-2026-49277 is a low-severity authentication bypass vulnerability in RocketChat Rocket.Chat, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-613
Which versions are affected by CVE-2026-49277?
How do I fix CVE-2026-49277?
No fix has been published for CVE-2026-49277 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-49277 being exploited?
There is no known exploitation of CVE-2026-49277 in the wild and no public exploit code.
Sources
Also known as GHSA-39hg-492f-3c4f.