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 integration does not verify the signature on inbound LogoutRequest messages. An unauthenticated remote attacker who knows a target user's SAML NameID - which major identity providers (Okta, Google Workspace, Microsoft Entra ID, JumpCloud) expose as the user's email address - can craft a valid-looking unsigned LogoutRequest and submit it to the SP logout endpoint. The server processes it as legitimate, immediately destroying the victim's session. Because the attack requires no authentication and no interaction from the victim, it can be repeated in a loop against individual users or scripted across many accounts, effectively rendering the Rocket.Chat instance unusable for SAML-authenticated users. 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.
CVE-2026-45677
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EPSS
- 36.4%
- KEV
- Not listed
Published
June 24, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jun 24, 2026Lack of SAML Signature Check During Logout Could Lead To DoS · Advisory · RocketChat/Rocket.Chat · GitHub
https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-pw6f-q8ww-vqfqWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 66× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 18:10 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 06:18 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 18:24 UTCEG score recompute
- 2026-07-14 06:32 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 18:35 UTCEG score recompute
- 2026-07-13 06:44 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 18:51 UTCEG score recompute
- 2026-07-12 06:59 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:07 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 07:15 UTCEG score recompute
- 2026-07-10 19:23 UTCEG score recompute
- 2026-07-10 07:32 UTCEG score recompute
- 2026-07-09 19:39 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 07:48 UTCEG score recompute
- 2026-07-08 19:56 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 08:04 UTCEG score recompute
- 2026-07-07 20:11 UTCEG score recompute
Show 41 moreShow fewer
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 08:19 UTCEG score recompute
- 2026-07-06 20:27 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 08:25 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 20:32 UTCEG score recompute
- 2026-07-05 08:40 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 20:48 UTCEG score recompute
- 2026-07-04 08:57 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:04 UTCEG score recompute
- 2026-07-03 09:12 UTCEG score recompute
- 2026-07-02 21:20 UTCEG score recompute
- 2026-07-02 09:29 UTCEG score recompute
- 2026-07-01 21:37 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 09:45 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 21:51 UTCEG score recompute
- 2026-06-30 09:59 UTCEG score recompute
- 2026-06-29 22:06 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 10:13 UTCEG score recompute
- 2026-06-28 22:20 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:29 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 22:37 UTCEG score recompute
- 2026-06-27 10:45 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 22:52 UTCEG score recompute
- 2026-06-26 11:00 UTCEG score recompute
- 2026-06-25 21:48 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 09:56 UTCEG score recompute
- 2026-06-24 22:03 UTCEG score recompute
- 2026-06-24 22:03 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-45677?
When was CVE-2026-45677 disclosed?
Is CVE-2026-45677 actively exploited?
What is the CVSS score of CVE-2026-45677?
How do I remediate CVE-2026-45677?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45677
Is Your Infrastructure Affected by CVE-2026-45677?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.