CVE-2026-46423: CWE-347: Improper Verification of Cryptographic Signature in RocketChat Rocket.Chat
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.
AI Analysis
Technical Summary
CVE-2026-46423 is a critical vulnerability in Rocket.Chat's SAML service provider implementation affecting versions prior to 7.10.11, 7.13.7, 8.0.5, 8.1.4, 8.2.3, 8.3.3, 8.4.1, and 8.5.0. The vulnerability arises because the verifySignatures routine returns early without validating SAML Response and Assertion signatures if the configured IdP certificate field is empty (which is the default). This results in a fail-open authentication bypass where unsigned or attacker-supplied assertions are accepted, exposing a publicly reachable SAML login endpoint without proper signature verification. The flaw is due to improper verification of cryptographic signatures (CWE-347).
Potential Impact
An attacker can bypass authentication by submitting unsigned or maliciously crafted SAML assertions to the affected Rocket.Chat SAML login endpoint if the IdP certificate is not configured. This allows unauthorized access without valid credentials, posing a critical security risk. The vulnerability affects default configurations where the IdP certificate field is empty, making it likely exploitable in default or misconfigured deployments.
Mitigation Recommendations
This vulnerability is fixed in Rocket.Chat versions 7.10.11, 7.13.7, 8.0.5, 8.1.4, 8.2.3, 8.3.3, 8.4.1, and 8.5.0. Administrators should upgrade to one of these fixed versions to remediate the issue. Until upgraded, ensure that the IdP certificate field is properly configured and not left empty when enabling SAML to avoid the fail-open signature verification behavior.
CVE-2026-46423: CWE-347: Improper Verification of Cryptographic Signature in RocketChat Rocket.Chat
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.
CVSS v4.0
Score 9.3critical
Affected software
pkg:github/rocketchat/Rocket.ChatRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-46423 is a critical vulnerability in Rocket.Chat's SAML service provider implementation affecting versions prior to 7.10.11, 7.13.7, 8.0.5, 8.1.4, 8.2.3, 8.3.3, 8.4.1, and 8.5.0. The vulnerability arises because the verifySignatures routine returns early without validating SAML Response and Assertion signatures if the configured IdP certificate field is empty (which is the default). This results in a fail-open authentication bypass where unsigned or attacker-supplied assertions are accepted, exposing a publicly reachable SAML login endpoint without proper signature verification. The flaw is due to improper verification of cryptographic signatures (CWE-347).
Potential Impact
An attacker can bypass authentication by submitting unsigned or maliciously crafted SAML assertions to the affected Rocket.Chat SAML login endpoint if the IdP certificate is not configured. This allows unauthorized access without valid credentials, posing a critical security risk. The vulnerability affects default configurations where the IdP certificate field is empty, making it likely exploitable in default or misconfigured deployments.
Mitigation Recommendations
This vulnerability is fixed in Rocket.Chat versions 7.10.11, 7.13.7, 8.0.5, 8.1.4, 8.2.3, 8.3.3, 8.4.1, and 8.5.0. Administrators should upgrade to one of these fixed versions to remediate the issue. Until upgraded, ensure that the IdP certificate field is properly configured and not left empty when enabling SAML to avoid the fail-open signature verification behavior.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T22:18:22.829Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c4ce24853345fc1df8d63
Added to database: 06/24/2026, 21:32:18 UTC
Last enriched: 07/01/2026, 22:34:42 UTC
Last updated: 08/07/2026, 21:30:31 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.