← Search results
CVE-LINKED INVENTORY85 SECURITY RECORDS
Zabbix
Zabbix
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Zabbix. Use that record for publisher support phases and retirement dates.
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-59788 | 5 Oct 2026 | Zabbix: 7.4.0 ≤ 7.4.11 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-59787 | 5 Oct 2026 | Zabbix: 6.0.0 ≤ 6.0.47, 7.0.0 ≤ 7.0.28, 7.4.0 ≤ 7.4.12 | Update the affected components and replace the deployed zabbix_trap_receiver.pl with the fixed version. | Update reference ↗ |
| CVE-2026-59786 | 5 Oct 2026 | Zabbix: 7.0.0 ≤ 7.0.28, 7.4.0 ≤ 7.4.12 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-59785 | 5 Oct 2026 | Zabbix: 6.0.0 ≤ 6.0.47, 7.0.0 ≤ 7.0.28, 7.4.0 ≤ 7.4.12 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-59783 | 5 Oct 2026 | Zabbix: 7.0.0 ≤ 7.0.28, 7.4.0 ≤ 7.4.12 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-59782 | 5 Oct 2026 | Zabbix: 6.0.0 ≤ 6.0.47, 7.0.0 ≤ 7.0.28, 7.4.0 ≤ 7.4.12 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-59781 | 18 Aug 2026 | Zabbix: 7.4.0 ≤ 7.4.12, 7.0.0 ≤ 7.0.28, 6.0.0 ≤ 6.0.47 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23938 | 18 Aug 2026 | Zabbix: 6.0.0 ≤ 6.0.46, 7.0.0 ≤ 7.0.26, 7.4.0 ≤ 7.4.10 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23937 | 18 Aug 2026 | Zabbix: 6.0.0 ≤ 6.0.46, 7.0.0 ≤ 7.0.27, 7.4.0 ≤ 7.4.11 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23935 | 18 Aug 2026 | Zabbix: 7.0.0 ≤ 7.0.27, 7.4.0 ≤ 7.4.11 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23934 | 18 Aug 2026 | Zabbix: 7.4.0 ≤ 7.4.11 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23933 | 18 Aug 2026 | Zabbix: 7.4.0 ≤ 7.4.10 | Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB. | Update reference ↗ |
| CVE-2026-23931 | 18 Aug 2026 | Zabbix: 7.4.0 ≤ 7.4.10 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23930 | 18 Aug 2026 | 6.0.0 ≤ 6.0.46; 7.0.0 ≤ 7.0.26; 7.4.0 ≤ 7.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23929 | 18 Aug 2026 | 6.0.44 ≤ 6.0.45; 7.0.22 ≤ 7.0.24; 7.4.6 ≤ 7.4.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-1199 | 18 Aug 2026 | 6.0.0 ≤ 6.0.46; 7.0.0 ≤ 7.0.27; 7.4.0 ≤ 7.4.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23922 | 18 Aug 2026 | 7.4.0 ≤ 7.4.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23928 | 6 May 2026 | Zabbix: 6.0.0 ≤ 6.0.44, 7.0.0 ≤ 7.0.23, 7.4.0 ≤ 7.4.7 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23927 | 6 May 2026 | Zabbix: 6.0.0 ≤ 6.0.44, 7.0.0 ≤ 7.0.23, 7.4.0 ≤ 7.4.7 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23926 | 6 May 2026 | Zabbix: 7.0.0 ≤ 7.0.23, 7.4.0 ≤ 7.4.7 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23924 | 24 Mar 2026 | Zabbix: 6.0.0 ≤ 6.0.43, 7.0.0 ≤ 7.0.22, 7.4.0 ≤ 7.4.6 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2026-23923 | 24 Mar 2026 | 7.4.0 ≤ 7.4.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23921 | 24 Mar 2026 | 7.0.0 ≤ 7.0.21; 7.2.0 ≤ 7.2.14; 7.4.0 ≤ 7.4.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23920 | 24 Mar 2026 | 7.0.0 ≤ 7.0.21; 7.2.0 ≤ 7.2.14; 7.4.0 ≤ 7.4.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23919 | 24 Mar 2026 | Zabbix: 6.0.0 ≤ 6.0.41, 7.0.0 ≤ 7.0.18, 7.2.0 ≤ 7.2.12, 7.4.0 ≤ 7.4.2 | Update the affected components to their respective fixed versions. Make sure JavaScript item preprocessing scripts don't store secret data in global variables. | Update reference ↗ |
| CVE-2026-23925 | 6 Mar 2026 | 6.0.0 ≤ 6.0.40; 7.0.0 ≤ 7.0.17; 7.4.0 ≤ 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-49643 | 1 Dec 2025 | Zabbix: 6.0.0 ≤ 6.0.41, 7.0.0 ≤ 7.0.18, 7.2.0 ≤ 7.2.12, 7.4.0 ≤ 7.4.2 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2025-49642 | 1 Dec 2025 | 6.0.0 ≤ 6.0.36; 7.0.0 ≤ 7.0.5; 7.2.0 < 7.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27232 | 1 Dec 2025 | Zabbix: 7.4.0 ≤ 7.4.2 | Update the affected components to their respective fixed versions. | Update reference ↗ |
| CVE-2025-49641 | 3 Oct 2025 | 6.0.0 ≤ 6.0.40; 7.0.0 ≤ 7.0.17; 7.2.0 ≤ 7.2.11; 7.4.0 ≤ 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27237 | 3 Oct 2025 | 6.0.0 ≤ 6.0.40; 7.0.0 ≤ 7.0.17; 7.2.0 ≤ 7.2.11; 7.4.0 ≤ 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27236 | 3 Oct 2025 | 6.0.38 ≤ 6.0.40; 7.0.9 ≤ 7.0.16; 7.2.3 ≤ 7.2.10; 7.4.0 < 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27231 | 3 Oct 2025 | 6.0.0 ≤ 6.0.40; 7.0.0 ≤ 7.0.17; 7.2.0 ≤ 7.2.11; 7.4.0 ≤ 7.4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27240 | 12 Sep 2025 | 6.0.0 ≤ 6.0.33; 6.4.0 ≤ 6.4.18; 7.0.0 ≤ 7.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27238 | 12 Sep 2025 | 7.0.0 ≤ 7.0.13; 7.2.0 ≤ 7.2.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27233 | 12 Sep 2025 | 6.0.0 ≤ 6.0.39; 7.0.0 ≤ 7.0.10; 7.2.0 ≤ 7.2.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27234 | 12 Sep 2025 | 5.0.0 ≤ 5.0.46 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45700 | 2 Apr 2025 | 6.0.0 ≤ 6.0.38; 7.0.0 ≤ 7.0.9; 7.2.0 ≤ 7.2.3 | 7.4.0alpha1 | Update reference ↗ |
| CVE-2024-45699 | 2 Apr 2025 | 6.0.0 ≤ 6.0.36; 6.4.0 ≤ 6.4.20; 7.0.0 ≤ 7.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42325 | 2 Apr 2025 | 5.0.0 ≤ 5.0.45; 6.0.0 ≤ 6.0.37; 7.0.0 ≤ 7.0.8; 7.2.0 ≤ 7.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36469 | 2 Apr 2025 | 5.0.0 ≤ 5.0.45; 6.0.0 ≤ 6.0.37; 7.0.0 ≤ 7.0.8; 7.2.0 ≤ 7.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36465 | 2 Apr 2025 | 7.0.0 ≤ 7.0.7; 7.2.0 ≤ 7.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36466 | 28 Nov 2024 | 6.0.0 ≤ 6.0.31; 6.4.0 ≤ 6.4.16; 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36464 | 27 Nov 2024 | 6.0.0 ≤ 6.0.29; 6.4.0 ≤ 6.4.15; 7.0.0alpha1 ≤ 7.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42333 | 27 Nov 2024 | 6.0.0 ≤ 6.0.33; 6.4.0 ≤ 6.4.18; 7.0.0 ≤ 7.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42332 | 27 Nov 2024 | 6.0.0 < 6.0.34; 6.4.0 < 6.4.19; 7.0.0 < 7.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42331 | 27 Nov 2024 | 7.0.0 ≤ 7.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42330 | 27 Nov 2024 | 6.0.0 ≤ 6.0.33; 6.4.0 ≤ 6.4.18; 7.0.0 ≤ 7.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42329 | 27 Nov 2024 | 7.0.0 ≤ 7.0.3rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42328 | 27 Nov 2024 | 7.0.0 ≤ 7.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.