CVE-2026-49277

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

Published Jun 24, 2026 CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed

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.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

RocketChat

Rocket.Chat

affected

Version	Status	Constraints
`>= 8.5.0-rc.0, < 8.5.0`	affected	—
`>= 8.4.0-rc.0, < 8.4.2`	affected	—
`>= 8.3.0-rc.0, < 8.3.4`	affected	—
`>= 8.2.0-rc.0, < 8.2.4`	affected	—
`>= 8.1.0-rc.0, < 8.1.5`	affected	—
`>= 8.0.0-rc.0, < 8.0.6`	affected	—
`>= 7.11.0-rc.0, < 7.13.8`	affected	—
`< 7.10.12`	affected	—

No data.

Vendor Product Versions

Rocketchat

Rocket.chat

Version	Status	Scheme	Platform
`[8.5.0-rc.0,8.5.0)`	affected	semver	—
`[8.4.0-rc.0,8.4.2)`	affected	semver	—
`[8.3.0-rc.0,8.3.4)`	affected	semver	—
`[8.2.0-rc.0,8.2.4)`	affected	semver	—
`[8.1.0-rc.0,8.1.5)`	affected	semver	—
`[8.0.0-rc.0,8.0.6)`	affected	semver	—
`[7.11.0-rc.0,7.13.8)`	affected	semver	—
`[0,7.10.12)`	affected	semver	—

Remediation

No solution or workaround provided in the CVE record

Tracking

Advisories

No advisories available

Metrics

Attack Vector Network

Attack Complexity High

Privileges Required None

Attack Requirements None

User Interaction Passive

Vulnerable System Confidentiality Impact Low

Vulnerable System Integrity Impact Low

Vulnerable System Availability Impact None

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.314% probability within 30 days)

Exploitation none

Automatable no

Technical Impact partial

References

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

History

Jun 26, 2026 7:30 PM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}`

Jun 25, 2026 6:15 AM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Rocketchat Rocketchat rocket.chat
Vendors & Products		Rocketchat Rocketchat rocket.chat

Jun 24, 2026 9:15 PM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
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.
Title		Rocket.Chat: OAuth access and refresh tokens remain valid after account deactivation
Weaknesses		CWE-613
References		https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-39hg-492f-3c4f
Metrics		cvssV4_0 `{'score': 2.3, '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'}`