Skip to content
major vulnerability· requires attention

Widely used enterprise chat platform; critical unauthenticated auth bypass with potential full instance compromise.

Web

CVE-2026-45688

9.1
Critical
EPSS 0.49%Patch availableJun 25, 2026

Unauthenticated CAS login bypass leads to token theft and full access.

common questions

Is CVE-2026-45688 being exploited?

Not confirmed. CVE-2026-45688 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.

How severe is CVE-2026-45688?

CVE-2026-45688 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-45688?

Yes. A fix has been recorded for CVE-2026-45688. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-45688 affect?

CVE-2026-45688 affects Rocket.Chat. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-45688?

Upgrade to patched release (>=8.5.0) and rotate credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Rocket.Chat
impact

NoSQL injection in credentialToken allows stealing a Meteor auth token bound to a victim, enabling full access and possible admin compromise.

action required

Immediate action required

affected versions
RocketChat Rocket.Chat
  • affected>= 8.5.0-rc.0 and < 8.5.0
  • affected>= 8.4.0-rc.0 and < 8.4.1
  • affected>= 8.3.0-rc.0 and < 8.3.3
  • affected>= 8.2.0-rc.0 and < 8.2.3
  • affected>= 8.1.0-rc.0 and < 8.1.4
  • affected>= 8.0.0-rc.0 and < 8.0.5
  • affected>= 7.11.0-rc.0 and < 7.13.7
  • affected< 7.10.11

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free