Complete end-of-life dates, support windows, and security status for all Zabbix versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.0 LTS | 4.0.50 | Oct 1, 2018 | Oct 31, 2023 | 921 days past EOL | EOL |
| 5.0 LTS | 5.0.47 | May 11, 2020 | May 31, 2025 | 343 days past EOL | EOL |
| 5.4 | 5.4.12 | May 17, 2021 | Mar 31, 2022 | 1500 days past EOL | EOL |
| 6.0 LTS | 6.0.46 | Feb 8, 2022 | Feb 28, 2027 | 295 days remaining | Active |
| 6.2 | 6.2.9 | Jul 4, 2022 | Feb 28, 2023 | 1166 days past EOL | EOL |
| 6.4 | 6.4.21 | Mar 6, 2023 | Dec 31, 2024 | 494 days past EOL | EOL |
| 7.0 LTS | 7.0.26 | Jun 4, 2024 | Jun 30, 2029 | 1148 days remaining | Active |
| 7.2 | 7.2.15 | Dec 10, 2024 | Dec 31, 2025 | 129 days past EOL | EOL |
| 7.4 | 7.4.10 | Jun 30, 2025 | Sep 30, 2026 | 144 days remaining | Warning |
When a Zabbix version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Zabbix should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →