Continued API access via unrevoked OAuth tokens
Published Jun 24, 2026 · Updated Jun 24, 2026
Insufficient token expiration in affected Rocket.Chat releases allows remote authenticated users to retain API access after deactivation. setUserActiveStatus revokes only Meteor login tokens, while OAuth bearer authentication omits the user.active check and refresh handling issues new access tokens without validating account state. Exploitation requires OAuth access or refresh credentials issued before an administrator deactivates the account, preserving the account's authorized read and write access.
Summary
What happened
Insufficient token expiration in affected Rocket.Chat releases allows remote authenticated users to retain API access after deactivation. setUserActiveStatus revokes only Meteor login tokens, while OAuth bearer authentication omits the user.active check and refresh handling issues new access tokens without validating account state. Exploitation requires OAuth access or refresh credentials issued before an administrator deactivates the account, preserving the account's authorized read and write access.
The record
- CVE
- CVE-2026-49277
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Rocket.Chat Technologies Corp.
- Product
- Rocket.Chat
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.10.12
- Affected versionversion=>= 7.11.0-rc.0, < 7.13.8
- Affected versionversion=>= 8.0.0-rc.0, < 8.0.6
- Affected versionversion=>= 8.1.0-rc.0, < 8.1.5
- Affected versionversion=>= 8.2.0-rc.0, < 8.2.4
- Affected versionversion=>= 8.3.0-rc.0, < 8.3.4
- Affected versionversion=>= 8.4.0-rc.0, < 8.4.2
- Affected versionversion=>= 8.5.0-rc.0, < 8.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-39hg-492f-3c4f proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo