CVE-2026-45677

Rocket.Chat: Lack of SAML Signature Check During Logout Could Lead To DoS

HIGH
8.7
CVSS Score
Published: June 24, 2026 at 08:54 PM UTC
Updated: October 25, 2026 at 10:10 PM UTC
1 product affected across 1 vendorChat Rocket Chat

Using Rocket.Chat by RocketChat?

Get instant alerts when new vulnerabilities affect Rocket.Chat - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

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 SAML integration does not verify the signature on inbound LogoutRequest messages. An unauthenticated remote attacker who knows a target user's SAML NameID - which major identity providers (Okta, Google Workspace, Microsoft Entra ID, JumpCloud) expose as the user's email address - can craft a valid-looking unsigned LogoutRequest and submit it to the SP logout endpoint. The server processes it as legitimate, immediately destroying the victim's session. Because the attack requires no authentication and no interaction from the victim, it can be repeated in a loop against individual users or scripted across many accounts, effectively rendering the Rocket.Chat instance unusable for SAML-authenticated users. 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 7.10.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.13.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.0.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.4.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.5.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-862

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card