Skip to main content
VulnerabilityPublished Updated

CVE-2026-46423: RocketChat Rocket.Chat · Improper Verification of Cryptographic Signature

Affects RocketChat Rocket.ChatSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical · fixed in 8.5.0 : patch RocketChat Rocket.Chat as a priority.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.0, 8.4.1, 8.3.3 +5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
RocketChatRocket.ChatAffected
  • >=8.5.0-rc.0 <8.5.0
Fixed in
  • 8.5.0
RocketChatRocket.ChatAffected
  • >=8.4.0-rc.0 <8.4.1
Fixed in
  • 8.4.1
RocketChatRocket.ChatAffected
  • >=8.3.0-rc.0 <8.3.3
Fixed in
  • 8.3.3
RocketChatRocket.ChatAffected
  • >=8.2.0-rc.0 <8.2.3
Fixed in
  • 8.2.3
RocketChatRocket.ChatAffected
  • >=8.1.0-rc.0 <8.1.4
Fixed in
  • 8.1.4
RocketChatRocket.ChatAffected
  • >=8.0.0-rc.0 <8.0.5
Fixed in
  • 8.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…