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

Back
New CVE Detected

CVE-2026-46423 – Authentication Bypass – Rocket.Chat (prior to 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4,…

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-46423 is a critical authentication bypass vulnerability in Rocket.Chat’s SAML service provider implementation, rated 9.3 (Critical) under CVSS 4.0. The flaw allows an unauthenticated remote attacker to forge or omit SAML assertion signatures and authenticate as any user — including administrators — on affected instances where SAML is enabled with an empty IdP certificate field. All Rocket.Chat installations running a vulnerable release with SAML enabled are at risk, spanning multiple major version branches.

Technical details

  • Root cause: The verifySignatures() routine performs an early return when serviceProviderOptions.cert is falsy. Because the IdP certificate field ships as an empty string by default, this fail-open branch is reached without any misconfiguration beyond leaving the field at its shipped default (CWE-347: Improper Verification of Cryptographic Signature).
  • Trigger conditions: SAML must be enabled by an administrator, and the IdP certificate field must be empty (its default value). No additional misconfiguration is required; the vulnerability is classified by the CVE record itself as a "default-configuration authentication-bypass class."
  • Attack vector: Network-accessible SAML login endpoint; no prior authentication, credentials, or user interaction required (CVSS 4.0: AV:N, AC:L, AT:N, PR:N, UI:N).
  • Impact: An attacker can supply unsigned or attacker-crafted SAML assertions, bypassing all signature validation and impersonating any workspace user, including administrators. This results in full account takeover, unauthorized data access, and potential full workspace compromise.

Affected software

  • Rocket.Chat < 7.10.11
  • Rocket.Chat 7.11.x – 7.13.x, prior to 7.13.7
  • Rocket.Chat 8.0.x, prior to 8.0.5
  • Rocket.Chat 8.1.x, prior to 8.1.4
  • Rocket.Chat 8.2.x, prior to 8.2.3
  • Rocket.Chat 8.3.x, prior to 8.3.3
  • Rocket.Chat 8.4.x, prior to 8.4.1
  • Rocket.Chat 8.5.x, prior to 8.5.0

Severity

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

Mitigation and recommended actions

  • Immediate — patch: Upgrade to one of the fixed releases: 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, 8.0.5, 7.13.7, or 7.10.11, depending on your current branch.
  • If patching is not immediately possible: Ensure the SAML IdP certificate field is populated with the correct certificate from your identity provider. An empty certificate field is the direct trigger for this vulnerability. Alternatively, disable SAML authentication until the patch can be applied.
  • Post-patch: Review SAML authentication logs for anomalous login activity that may indicate prior exploitation — particularly logins with no matching IdP session or logins for high-privilege accounts.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge