CVE-2026-45757: RocketChat Rocket.Chat · Insufficient Session Expiration
Affects RocketChat Rocket.ChatSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low · fixed in 8.5.0 : update RocketChat Rocket.Chat when convenient.
Data as of 5 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.5.0, 8.4.2, 8.3.4 +5
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
| RocketChatRocket.Chat | Affected
| Fixed in
|
AI-suggested
The vulnerability is fixed in Rocket.Chat 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. Users should upgrade to one of these fixed versions to remediate the issue. Patch status is not explicitly confirmed beyond the stated fixed versions, so verifying with the vendor advisory is recommended for current remediation guidance.
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 allows users deactivated through users.deactivateIdle to keep using already-issued login tokens. A user that an administrator has marked inactive for idleness can still access authenticated REST endpoints with the old 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.