Continued API access via unrevoked login tokens
Published Jun 24, 2026 · Updated Jun 24, 2026
Insufficient session expiration in Rocket.Chat affected releases allows remote authenticated users to retain REST API access after deactivation. users.deactivateIdle changes active and inactiveReason but leaves services.resume.loginTokens intact, while REST authentication accepts the stored token without checking active status. Exploitation requires a valid token issued before an administrator runs users.deactivateIdle; the deactivated account retains its existing permissions on authenticated REST endpoints.
Summary
What happened
Insufficient session expiration in Rocket.Chat affected releases allows remote authenticated users to retain REST API access after deactivation. users.deactivateIdle changes active and inactiveReason but leaves services.resume.loginTokens intact, while REST authentication accepts the stored token without checking active status. Exploitation requires a valid token issued before an administrator runs users.deactivateIdle; the deactivated account retains its existing permissions on authenticated REST endpoints.
The record
- CVE
- CVE-2026-45757
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Rocket.Chat Technologies Corp.
- Product
- Rocket.Chat
- Classifications
- CWE-613, T1078
- 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.
Public exploit references
- GHSA-6g3w-vg5p-w892 REST token-reuse 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