CVE-2026-58066: Rocket.Chat's SAML SSO before versions 8.7.0, 8.6.1, 8.5.2, 8.4.5, 8.3.7, 8.2.7, 8.1.7, 8.0.8, and 7.10.14 verified XML signatures but did not bind
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 8.7.0 : patch affected systems as a priority.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.7.0, 8.6.1, 8.5.2 +6
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
AI-suggested
Fixed versions are 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, 8.6.1, and 8.7.0. Users should upgrade to these or later versions to remediate the vulnerability. Since this is not a cloud service, remediation depends on user action.
Description
Rocket.Chat versions prior to 7.10.14 and various 8.x releases did not properly bind verified XML signatures to the corresponding SAML Response or Assertion. This flaw allowed an attacker to submit a wrapped SAML document containing forged identity attributes alongside a valid signature from a trusted identity provider, enabling unauthorized login as arbitrary users.