Rocket.Chat

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at rocket.chat, but registry activity is not a publisher support boundary.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2026-75575	25 Aug 2026	< 7.10.15; 8.0.0 < 8.1.8; 8.2.0 < 8.2.8; 8.3.0 < 8.3.8; 8.4.0 < 8.4.6; 8.5.0 < 8.5.3; 8.6.0 < 8.6.2; 8.7.0 < 8.7.2	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-72919	10 Aug 2026	< 7.10.14; >= 8.0.0, < 8.0.8; >= 8.1.0, < 8.1.7; >= 8.2.0, < 8.2.7; >= 8.3.0, < 8.3.7; >= 8.4.0, < 8.4.5; >= 8.5.0, < 8.5.2; >= 8.6.0, < 8.6.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-72918	10 Aug 2026	< 7.10.14; >= 8.0.0, < 8.0.8; >= 8.1.0, < 8.1.7; >= 8.2.0, < 8.2.7; >= 8.3.0, < 8.3.7; >= 8.4.0, < 8.4.5; >= 8.5.0, < 8.5.2; >= 8.6.0, < 8.6.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-55762	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.1; >= 8.4.0-rc.0, < 8.4.4; >= 8.3.0-rc.0, < 8.3.6; >= 8.2.0-rc.0, < 8.2.6; >= 8.1.0-rc.0, < 8.1.6; >= 7.11.0-rc.0, < 8.0.7; < 7.10.13	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-55759	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.1; >= 8.4.0-rc.0, < 8.4.4; >= 8.3.0-rc.0, < 8.3.6; >= 8.2.0-rc.0, < 8.2.6; >= 8.1.0-rc.0, < 8.1.6; >= 7.11.0-rc.0, < 8.0.7; < 7.10.13	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-55666	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.1; >= 8.4.0-rc.0, < 8.4.4; >= 8.3.0-rc.0, < 8.3.6; >= 8.2.0-rc.0, < 8.2.6; >= 8.1.0-rc.0, < 8.1.6; >= 7.11.0-rc.0, < 8.0.7; < 7.10.13	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-49278	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.2; >= 8.3.0-rc.0, < 8.3.4; >= 8.2.0-rc.0, < 8.2.4; >= 8.1.0-rc.0, < 8.1.5; >= 8.0.0-rc.0, < 8.0.6; >= 7.11.0-rc.0, < 7.13.8; < 7.10.12	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-49277	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.2; >= 8.3.0-rc.0, < 8.3.4; >= 8.2.0-rc.0, < 8.2.4; >= 8.1.0-rc.0, < 8.1.5; >= 8.0.0-rc.0, < 8.0.6; >= 7.11.0-rc.0, < 7.13.8; < 7.10.12	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-45757	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.2; >= 8.3.0-rc.0, < 8.3.4; >= 8.2.0-rc.0, < 8.2.4; >= 8.1.0-rc.0, < 8.1.5; >= 8.0.0-rc.0, < 8.0.6; >= 7.11.0-rc.0, < 7.13.8; < 7.10.12	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-46423	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.1; >= 8.3.0-rc.0, < 8.3.3; >= 8.2.0-rc.0, < 8.2.3; >= 8.1.0-rc.0, < 8.1.4; >= 8.0.0-rc.0, < 8.0.5; >= 7.11.0-rc.0, < 7.13.7; < 7.10.11	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-45689	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.1; >= 8.3.0-rc.0, < 8.3.3; >= 8.2.0-rc.0, < 8.2.3; >= 8.1.0-rc.0, < 8.1.4; >= 8.0.0-rc.0, < 8.0.5; >= 7.11.0-rc.0, < 7.13.7; < 7.10.11	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-45688	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.1; >= 8.3.0-rc.0, < 8.3.3; >= 8.2.0-rc.0, < 8.2.3; >= 8.1.0-rc.0, < 8.1.4; >= 8.0.0-rc.0, < 8.0.5; >= 7.11.0-rc.0, < 7.13.7; < 7.10.11	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-45687	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.1; >= 8.3.0-rc.0, < 8.3.3; >= 8.2.0-rc.0, < 8.2.3; >= 8.1.0-rc.0, < 8.1.4; >= 8.0.0-rc.0, < 8.0.5; >= 7.11.0-rc.0, < 7.13.7; < 7.10.11	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-45677	24 Jun 2026	>= 8.5.0-rc.0, < 8.5.0; >= 8.4.0-rc.0, < 8.4.1; >= 8.3.0-rc.0, < 8.3.3; >= 8.2.0-rc.0, < 8.2.3; >= 8.1.0-rc.0, < 8.1.4; >= 8.0.0-rc.0, < 8.0.5; >= 7.11.0-rc.0, < 7.13.7; < 7.10.11	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-47733	24 Jun 2026	< 8.5.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-30833	6 Mar 2026	< 7.10.8; < 7.11.5; < 7.12.5; < 7.13.4; < 8.0.2; < 8.1.1; < 8.2.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-30831	6 Mar 2026	< 7.10.8; < 7.11.5; < 7.12.5; < 7.13.4; < 8.0.2; < 8.1.1; < 8.2.0	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2026-28514	6 Mar 2026	< 7.8.6; < 7.9.8; < 7.10.7; < 7.11.4; < 7.12.4; < 7.13.3; < 8.0.0	An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.	Update reference ↗
CVE-2026-23477	14 Jan 2026	< 6.12.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2021-32832	30 Aug 2021	< 3.11.3	An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.	Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.