CVE-2026-46423 Details
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.
A vulnerability in Rocket.Chat's SAML service provider implementation allows for authentication bypass when the IdP certificate field is left empty. In versions 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, the SAML Response and Assertion signature validations are silently skipped if the certificate field is not populated. This oversight occurs because the default setting for the certificate is an empty string, and the provider registration process does not require a certificate to be present. As a result, an administrator who enables SAML without providing a certificate exposes a publicly accessible SAML login endpoint that accepts unsigned or manipulated assertions. This vulnerability allows remote attackers to impersonate users, including administrators, by exploiting the SAML authentication flow.
To address this vulnerability, the SAML signature verifier should be modified to reject empty certificate fields and throw an error instead of returning early. Additionally, a server-side settings validator should be implemented to prevent the SAML provider from being enabled without a valid certificate. This validation should be reflected in the settings UI to alert administrators of the misconfiguration.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jun 24, 2026CISA-ADP
Assessed Jun 25, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-rgg7-qvp9-wvx7 | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-347 | Improper Verification of Cryptographic Signature | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Rocket.Chat | < 8.5.0 (semver) < 8.4.1 (semver) < 8.3.3 (semver) < 8.2.3 (semver) < 8.1.4 (semver) < 8.0.5 (semver) < 7.13.7 (semver) < 7.10.11 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 26, 2026 | CVE Modified | CISA-ADP |
| Jun 25, 2026 | CVE Modified | CISA-ADP |
| Jun 24, 2026 | New CVE Received | [email protected] |
Volerion