← Search results
CVE-LINKED INVENTORY32 SECURITY RECORDS
zulip
zulip
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 zulip, 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-40300 | 12 May 2026 | < 12.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-26058 | 3 Apr 2026 | >= 1.4.0, < 11.6 | 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-25742 | 3 Apr 2026 | < 11.6 | 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-25741 | 26 Feb 2026 | < bf28c82dc9b1f630fa8e9106358771b20a0040f7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-24050 | 6 Feb 2026 | >= 5.0, < 11.5 | 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-2025-52559 | 2 Jul 2025 | >= 2.0.0-rc1, < 10.4 | 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-2025-47930 | 15 May 2025 | >= 10.0, < 10.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 ↗ |
| CVE-2025-31478 | 16 Apr 2025 | < 10.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-30369 | 31 Mar 2025 | >= 1.6.0, < 10.1 | 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-2025-30368 | 31 Mar 2025 | >= 10.0-beta1, < 10.1 | 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-2025-27149 | 31 Mar 2025 | >= 2.1.0, < 10.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-25195 | 13 Feb 2025 | >= 50256f48314250978f521ef439cafa704e056539, < 75be449d456d29fef27e9d1828bafa30174284b4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-56136 | 16 Jan 2025 | >= 7.0, < 9.4 | 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-2024-27286 | 20 Mar 2024 | >= 3.0, < 8.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 ↗ |
| CVE-2024-21630 | 25 Jan 2024 | = 8.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-2023-47642 | 16 Nov 2023 | >= 1.3.0, < 7.5 | 7.5 | Update reference ↗ |
| CVE-2023-32678 | 25 Aug 2023 | < 7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-33186 | 30 May 2023 | >= 7.0-beta1, < 7.0-beta3 | 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-2023-28623 | 19 May 2023 | >= 2.1.0, < 6.2 | 6.2. | Update reference ↗ |
| CVE-2023-32677 | 19 May 2023 | > 1.9.0, < 6.2 | 6.2. | Update reference ↗ |
| CVE-2023-22735 | 7 Feb 2023 | >= 04cf68b, < 2f6c5a8 | 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-2022-41914 | 16 Nov 2022 | >= 5.0, < 5.7 | 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-2022-36048 | 31 Aug 2022 | < 5.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-31168 | 22 Jul 2022 | < 5.5 | 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-2022-31134 | 12 Jul 2022 | >= 2.1.0, < 5.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-31017 | 25 Jun 2022 | >= 2.1.0, < 5.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-24751 | 16 Mar 2022 | >= 4.0, < 4.11 | 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-2022-23656 | 2 Mar 2022 | >= 2021-06-03, < 2022-03-01 | 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-2022-21706 | 25 Feb 2022 | >= 2.0.0, < 4.10 | 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-2021-43799 | 25 Jan 2022 | < 4.9 | 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-2021-43791 | 2 Dec 2021 | < 4.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 ↗ |
| CVE-2021-41115 | 7 Oct 2021 | < 4.7 | 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.