Quick answers
- Is CVE-2026-45757 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45757 being exploited in the wild.
- How severe is CVE-2026-45757?
- 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-45757?
- 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-45757 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45757?
- 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 session-revocation vulnerability exists in Rocket.Chat's 'users.deactivateIdle' functionality. While the standard deactivation path correctly calls 'Users.unsetLoginTokens', the idle deactivation route only updates the user's active status and 'inactiveReason' without clearing 'services.resume.loginTokens'. Because the REST API authentication logic validates the hashed token without verifying if the 'active' flag is set to true, deactivated users can continue to interact with authenticated endpoints. This 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: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD