Skip to main content
VulnerabilityPublished Updated

CVE-2026-45688: RocketChat Rocket.Chat · Improper Neutralization of Special Elements in Data Query Logic

Affects RocketChat Rocket.ChatSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 8.5.0 : patch RocketChat Rocket.Chat as a priority.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.1
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.0, 8.4.1, 8.3.3 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
RocketChatRocket.ChatAffected
  • >=8.5.0-rc.0 <8.5.0
Fixed in
  • 8.5.0
RocketChatRocket.ChatAffected
  • >=8.4.0-rc.0 <8.4.1
Fixed in
  • 8.4.1
RocketChatRocket.ChatAffected
  • >=8.3.0-rc.0 <8.3.3
Fixed in
  • 8.3.3
RocketChatRocket.ChatAffected
  • >=8.2.0-rc.0 <8.2.3
Fixed in
  • 8.2.3
RocketChatRocket.ChatAffected
  • >=8.1.0-rc.0 <8.1.4
Fixed in
  • 8.1.4
RocketChatRocket.ChatAffected
  • >=8.0.0-rc.0 <8.0.5
Fixed in
  • 8.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Rocket.Chat versions 7.10.11, 7.13.7, 8.0.5, 8.1.4, 8.2.3, 8.3.3, 8.4.1, and 8.5.0. Users should upgrade to one of these versions or later to remediate the issue. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes. Patch status is not explicitly confirmed beyond the stated fixed versions; therefore, verify with official Rocket.Chat advisories for current remediation guidance.

Description

Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 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, Rocket.Chat's CAS login handler forwards the client-supplied options.cas.credentialToken value straight into a MongoDB findOne({_id: ...}) query without any runtime type check. TypeScript's string parameter annotation is erased at runtime, so an unauthenticated attacker can substitute a MongoDB query operator ({"$gt": ""}, {"$ne": null}, etc.) for what the server expects to be an opaque ticket string. The injected operator matches the first unexpired document in the credential_tokens collection, bypassing the CAS ticket check entirely. When any legitimate CAS or SAML SSO login is in flight, the attacker's next DDP login call matches the same credential-token row via the NoSQL operator and is issued a full Meteor auth token (userId + token) bound to the victim. The token is immediately usable against the complete REST and DDP surface as that user. If the victim is an administrator, this escalates to full instance compromise via Apps-Engine app install. This vulnerability is fixed in 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.

References

Community reviews

Loading reviews…