← Search results
CVE-LINKED INVENTORY26 SECURITY RECORDS
Publisher not identified
Rocket.chat
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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-2023-28359 | 11 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28358 | 11 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28357 | 11 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28356 | 11 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28325 | 11 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28318 | 9 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28317 | 9 May 2023 | This issue has been fixed in version 6.0> and is backported for the supported versions. Check this document for more info: https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-28316 | 9 May 2023 | Fixed in 6.0> and back-ported accordingly to our supported versions. Check https://docs.rocket.chat/resources/get-support/enterprise-support#rocket.chat-versions for more info | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-23911 | 10 Mar 2023 | fixed version => 6.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-23917 | 23 Feb 2023 | Fixed Version => 5.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32220 | 23 Sep 2022 | fixed in 5.0.0> | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-32219 | 23 Sep 2022 | fixed in 4.7.5> | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-32217 | 23 Sep 2022 | fixed in 4.6.4> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32211 | 23 Sep 2022 | Fixed in 3.18.6, 4.4.4 and 4.7.3> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-35247 | 23 Sep 2022 | Fixed in versions 4.7.5, 4.8,2 and 5.0.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32229 | 23 Sep 2022 | Fixed in version 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32228 | 23 Sep 2022 | Fixed in versions 4.7.5, 4.8.2 and 5.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32227 | 23 Sep 2022 | Fixed in versions 4.7.5, 4.8.2, 5.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32226 | 23 Sep 2022 | Fixed in 4.7.5, 4.8.2 and 5.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32218 | 23 Sep 2022 | Fixed in 4.7.5, 4.8.2 and 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-35251 | 23 Sep 2022 | Fixed in 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-35250 | 23 Sep 2022 | Fixed in 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-35249 | 23 Sep 2022 | Fixed in version 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-35248 | 23 Sep 2022 | Fixed in versions 4.7.5, 4.8.2, 5.0.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-35246 | 23 Sep 2022 | Fixed in versions 4.7.5, 4.8.2 and 5.0> | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-22886 | 26 Mar 2021 | Fixed in 3.11, 3.10.5, 3.9.7, 3.8.8 | 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.