Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-45677 – Unauthenticated SAML Logout Spoofing Leading to Platform-Wide DoS – Rocket.Chat …

Be the first to know when new zero-days emerge:

Summary

CVE-2026-45677 is a high-severity missing authorization vulnerability in Rocket.Chat’s SAML integration that allows an unauthenticated remote attacker to forcibly terminate any SAML-authenticated user’s session by submitting an unsigned LogoutRequest to the service provider logout endpoint. Rated CVSS 4.0: 8.7 (HIGH), the flaw can be automated at scale to render an entire Rocket.Chat deployment unusable for all SAML-authenticated users, constituting a platform-wide availability attack.

Technical details

  • Root cause: Rocket.Chat’s SAML implementation does not verify the cryptographic signature on inbound LogoutRequest messages (CWE-862: Missing Authorization). The server accepts and processes unsigned logout requests as legitimate, immediately destroying the targeted session.
  • Trigger conditions: The vulnerability is exploitable on any Rocket.Chat instance where SAML-based single sign-on has been enabled and configured. The attacker must know a target user’s SAML NameID — which major identity providers (Okta, Google Workspace, Microsoft Entra ID, JumpCloud) expose as the user’s email address.
  • Attack vector: Network-based, fully unauthenticated, no user interaction required. An attacker crafts an unsigned LogoutRequest containing the victim’s NameID and submits it directly to the SAML SP logout endpoint over HTTP/HTTPS.
  • Impact: Immediate and silent session destruction for the targeted user. Because the attack requires no authentication and can be scripted against a list of known email addresses, it can be executed in a loop across all SAML-authenticated accounts, effectively locking every user out of the platform and rendering it operationally unavailable. There is no confidentiality or integrity impact.

Affected software

  • Rocket.Chat all versions prior to 7.10.11
  • Rocket.Chat 7.11.x through versions prior to 7.13.7
  • Rocket.Chat 8.0.x through versions prior to 8.0.5
  • Rocket.Chat 8.1.x through versions prior to 8.1.4
  • Rocket.Chat 8.2.x through versions prior to 8.2.3
  • Rocket.Chat 8.3.x through versions prior to 8.3.3
  • Rocket.Chat 8.4.x through versions prior to 8.4.1
  • Rocket.Chat 8.5.x release candidates prior to 8.5.0

Severity

CVSS 4.0 Base Score: 8.7 (HIGH)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score reflects a network-based, zero-complexity, unauthenticated attack with high availability impact and no confidentiality or integrity compromise.

Mitigation and recommended actions

  • Immediate action — patch: Upgrade to one of the fixed releases that corresponds to your current branch:
    • 8.5.0 (latest stable)
    • 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5 (patch releases for active branches)
    • 7.13.7, 7.10.11 (patch releases for older supported branches)
  • If immediate patching is not feasible: No vendor-documented workarounds have been published. Organizations that cannot patch immediately should assess the operational risk and consider restricting network access to the SAML logout endpoint at the perimeter, or temporarily disabling SAML SSO until the upgrade can be applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge