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

New CVE Detected

CVE-2026-58066 – Authentication Bypass – Rocket.Chat SAML SSO before 8.7.0

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

Summary

CVE-2026-58066 is a critical SAML XML Signature Wrapping (XSW) authentication bypass vulnerability in Rocket.Chat’s SSO implementation, affecting all versions before 8.7.0 and multiple prior stable branches. With a CVSS score of 9.8 (Critical), an unauthenticated remote attacker can craft a malicious SAML document to forge identity attributes and authenticate as any arbitrary user — including administrators — without valid credentials. Rocket.Chat has released patched versions across all affected branches.

Technical details

  • Root cause: Rocket.Chat’s SAML service provider verified that an inbound XML signature was cryptographically valid against the trusted Identity Provider (IdP) certificate, but never bound that validated signature to the specific samlp:Response or saml:Assertion element being processed (CWE-287: Improper Authentication). This decoupling is the defining flaw of XML Signature Wrapping (XSW) attacks.
  • Trigger conditions: SAML SSO must be configured on the Rocket.Chat instance. SAML/SSO integration is a common enterprise deployment pattern for Rocket.Chat.
  • Attack vector: A remote, unauthenticated attacker submits a specially crafted SAML document that wraps forged identity attributes alongside a legitimately signed XML node obtained from the trusted IdP. Because signature validation succeeds against the legitimate node, the Rocket.Chat service provider accepts the forged assertion and issues a session for the targeted account.
  • Impact: Complete authentication bypass — the attacker can log in as any user, including workspace administrators — resulting in full compromise of confidentiality, integrity, and availability of the affected Rocket.Chat instance. Per CISA’s SSVC assessment, the vulnerability is automatable with total technical impact.

Affected software

  • Rocket.Chat versions before 8.7.0 (latest stable branch)
  • Rocket.Chat versions before 8.6.1 (8.6.x stable branch)
  • Rocket.Chat versions before 8.5.2 (8.5.x stable branch)
  • Rocket.Chat versions before 8.4.5 (8.4.x stable branch)
  • Rocket.Chat versions before 8.3.7 (8.3.x stable branch)
  • Rocket.Chat versions before 8.2.7 (8.2.x stable branch)
  • Rocket.Chat versions before 8.1.7 (8.1.x stable branch)
  • Rocket.Chat versions before 8.0.8 (8.0.x stable branch)
  • Rocket.Chat versions before 7.10.14 (7.10.x stable branch)

Severity

CVSS v3.0 base score: 9.8 (Critical)
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate — patch: Upgrade to one of the fixed releases corresponding to your deployment branch: 8.7.0, 8.6.1, 8.5.2, 8.4.5, 8.3.7, 8.2.7, 8.1.7, 8.0.8, or 7.10.14. The upstream fix was backported across all active stable branches (see GitHub PR #41233).
  • If immediate patching is not feasible: Temporarily disable SAML SSO in Rocket.Chat’s Administration → SSO settings until the patch can be applied. This removes the attack surface entirely, as the vulnerability is only exploitable when SAML SSO is active.
  • Detection: Review authentication logs for anomalous SAML-based login events — particularly logins attributed to administrator accounts originating from unexpected sources or at unusual times.

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