Quick answers
- Is CVE-2026-45689 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45689 being exploited in the wild.
- How severe is CVE-2026-45689?
- Critical severity, with a CVSS score of 9.1, published 24 June 2026.
- Which products and versions are affected?
- Rocket.Chat < 8.5.0, < 8.4.1, < 8.3.3, < 8.2.3, < 8.1.4, < 8.0.5, < 7.13.7, < 7.10.11.
- Is there a fix for CVE-2026-45689?
- 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-45689 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45689?
- 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 NoSQL injection vulnerability exists in the `/oauth/token` endpoint of Rocket.Chat due to improper validation of grant parameters. The application fails to ensure that `client_id`, `client_secret`, and `refresh_token` are strings before passing them to MongoDB `findOne()` queries. An unauthenticated attacker can provide MongoDB query operators (e.g., `{"$ne": null}`) in a JSON POST request to bypass client authentication and retrieve the first available refresh token from the database. By using operators like `$nin` or `$regex`, an attacker can iterate through the `oauth_access_tokens` collection to harvest access tokens for all users. If an administrator's token is retrieved, the attacker gains full API access, which can be leveraged for server-side code execution via the Apps-Engine. The issue is fixed in versions 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, and 7.10.11.
Affected products
- RocketChat Rocket.Chat < 8.5.0, < 8.4.1, < 8.3.3, < 8.2.3, < 8.1.4, < 8.0.5, < 7.13.7, < 7.10.11
Timeline
- 2026-05-14: advisory: Original GitHub security advisory published
- 2026-06-24: disclosed: CVE published to NVD