Zabbix 8.0 · Version Status
Zabbix 8.0 End of Life Date
Zabbix 8.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Zabbix 8.0 is actively supported. EOL date: November 30, 2031.
📅 Get reminded before Zabbix 8.0 reaches EOL on November 30, 2031 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 30, 2031
1851 days remaining
Latest Release
8.0.0
LTS release
Release Date
Nov 5, 2026
Zabbix 8.0 series
Where these dates come from
End of lifeNov 30, 2031Vendor's own page (our correction) · zabbix.com · checked Nov 5, 2026medium · 1 source agrees End of active supportNov 30, 2029Vendor's own page (our correction) · zabbix.com · checked Nov 5, 2026medium · 1 source agrees ReleaseNov 5, 2026Vendor's own page (our correction) · zabbix.com · checked Nov 5, 2026medium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Zabbix 8.0 was released on November 5, 2026 and support is scheduled to end on November 30, 2031 — a planned supported lifespan of 5 years and 1 month, in line with the 5 years and 1 month median for Zabbix LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 8.0.0, published November 5, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
| Version | Latest | EOL Date | Status |
|---|
| 4.0 LTS |
4.0.50 |
Oct 31, 2023 |
EOL |
| 5.0 LTS |
5.0.47 |
May 31, 2025 |
EOL |
| 5.4 |
5.4.12 |
Mar 31, 2022 |
EOL |
| 6.0 LTS |
6.0.49 |
Feb 28, 2027 |
Warning |
| 6.2 |
6.2.9 |
Feb 28, 2023 |
EOL |
| 6.4 |
6.4.21 |
Dec 31, 2024 |
EOL |
| 7.0 LTS |
7.0.32 |
Jun 30, 2029 |
Active |
| 7.2 |
7.2.15 |
Dec 31, 2025 |
EOL |
What does Zabbix 8.0 end of life mean?
When Zabbix 8.0 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Zabbix 8.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Zabbix 8.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Zabbix 8.0 reach end of life?
Zabbix 8.0 reaches end of life on November 30, 2031. That is 1851 days remaining.
Is Zabbix 8.0 still supported?
Yes, Zabbix 8.0 is currently supported. The EOL date is November 30, 2031.
What should I upgrade to from Zabbix 8.0?
The recommended upgrade from Zabbix 8.0 is
Zabbix 8.0 — the latest actively supported version. Check the
Zabbix full timeline for all supported versions.
What are the security risks of running Zabbix 8.0 past EOL?
When Zabbix 8.0 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Zabbix should migrate immediately or implement compensating controls.