Is CVE-2026-49277 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49277 being exploited in the wild.

How severe is CVE-2026-49277?

Informational severity, with a CVSS score of 2.3, published 24 June 2026.

Which products and versions are affected?

Rocket.Chat < 8.5.0, < 8.4.2, < 8.3.4, < 8.2.4, < 8.1.5, < 8.0.6, < 7.13.8, < 7.10.12.

Is there a fix for CVE-2026-49277?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-49277 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-49277?

Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49277: Rocket.Chat OAuth token persistence after account deactivation

Q: Which products and versions are affected?

Rocket.Chat < 8.5.0, < 8.4.2, < 8.3.4, < 8.2.4, < 8.1.5, < 8.0.6, < 7.13.8, < 7.10.12.

Q: Is there a fix for CVE-2026-49277?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-49277 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-49277?

Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49277 · Severity: info · CVSS 2.3 · Published 2026-06-24

Rocket.Chat is a customizable communications platform used for team collaboration. A security flaw allows deactivated users to maintain access to the platform if they have active OAuth tokens. This means an employee or user whose account was disabled by an administrator could still read messages or interact with the API, potentially leading to unauthorized data access or continued presence in private communications.

Technologies: Rocket.Chat. Vendors: Rocket.Chat.

Quick answers

Is CVE-2026-49277 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49277 being exploited in the wild.
How severe is CVE-2026-49277?: Informational severity, with a CVSS score of 2.3, published 24 June 2026.
Which products and versions are affected?: Rocket.Chat < 8.5.0, < 8.4.2, < 8.3.4, < 8.2.4, < 8.1.5, < 8.0.6, < 7.13.8, < 7.10.12.
Is there a fix for CVE-2026-49277?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-49277 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-49277?: Check whether you run Rocket.Chat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in Rocket.Chat's OAuth implementation results in insufficient session expiration (CWE-613). When a user is deactivated via the `setUserActiveStatus` function, the system revokes Meteor login tokens but fails to invalidate OAuth access or refresh tokens. Furthermore, the OAuth bearer authentication and refresh-token handling logic do not verify the user's 'active' status before authorizing requests or issuing new tokens. An attacker with a previously established OAuth session can continue to access protected API endpoints and mint new access tokens even after their account has been administratively disabled. The issue is resolved in versions 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.

Affected products

RocketChat Rocket.Chat < 8.5.0, < 8.4.2, < 8.3.4, < 8.2.4, < 8.1.5, < 8.0.6, < 7.13.8, < 7.10.12

Timeline

2026-05-25: advisory: Original GitHub security advisory published
2026-06-24: disclosed: CVE published to NVD

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.