Zabbix 7.2
Zabbix 7.2
The Zabbix 7.2 reached end of service life on Dec 31, 2025 — Zabbix no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Zabbix 7.2 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- zabbix
- release
- 7.2
- product Label
- Zabbix
- release Label
- 7.2
- codename
- lts
- latest Version
- 7.2.15
- release Date
- 2024-12-10
- maintained
- source Url
- https://endoflife.date/zabbix
Lifecycle Dates
- End of Service Life
- Dec 31, 2025
- Last OEM Support
- Jun 30, 2025
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Zabbix 7.2 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Zabbix 7.2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Zabbix 7.2 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Zabbix 7.2 Support: Frequently Asked Questions
Is the Zabbix 7.2 still supported?
Zabbix ended support for the Zabbix 7.2 on Dec 31, 2025 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Zabbix 7.2 end of service life (EOSL) date?
Zabbix lists the end of service life for the Zabbix 7.2 as Dec 31, 2025.
Can I keep using the Zabbix 7.2 after its EOSL date?
Yes. EOSL means Zabbix stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Zabbix 7.2 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting Zabbix 7.2
10 published CVEs affect the Zabbix 7.2, including 4 rated critical or high severity. Zabbix no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-23921 | HIGH | 8.7 | Mar 24, 2026 | A low privilege Zabbix user with API access can exploit a blind SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL selects via the sortfield parameter. Although query results are not returned directly, an attacker can exfiltrate arbitrary database data through time-based techniques, potentially leading to session identifier disclosure and administrator account compromise. |
| CVE-2024-36465 | HIGH | 8.6 | Apr 2, 2025 | A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter. |
| CVE-2026-23920 | HIGH | 7.7 | Mar 24, 2026 | Host and event action script input is validated with a regex (set by the administrator), but the validation runs in multiline mode. If ^ and $ anchors are used in user input validation, an injected newline lets authenticated users bypass the check and inject shell commands. |
| CVE-2026-23919 | HIGH | 7.1 | Mar 24, 2026 | For performance reasons Zabbix Server/Proxy reuses JavaScript (Duktape) contexts (used in script items, JavaScript reprocessing, Webhooks). This can lead to confidentiality loss where a regular (non-super) Zabbix administrator leaks data for hosts they do not have access to. A fix has been released that makes the built in Zabbix JavaScript objects read-only, but please be advised that usage of global JavaScript variables is not recommended because their content could be leaked. More information |
| CVE-2024-45700 | MEDIUM | 6.0 | Apr 2, 2025 | Zabbix server is vulnerable to a DoS vulnerability due to uncontrolled resource exhaustion. An attacker can send specially crafted requests to the server, which will cause the server to allocate an excessive amount of memory and perform CPU-intensive decompression operations, ultimately leading to a service crash. |
| CVE-2025-49641 | MEDIUM | 5.1 | Oct 3, 2025 | A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.view.refresh action and therefore still retrieve a list of active problems. |
| CVE-2025-27231 | MEDIUM | 4.3 | Oct 3, 2025 | The LDAP 'Bind password' value cannot be read after saving, but a Super Admin account can leak it by changing LDAP 'Host' to a rogue LDAP server. To mitigate this, the 'Bind password' value is now reset on 'Host' change. |
| CVE-2024-36469 | LOW | 2.3 | Apr 2, 2025 | Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one. |
| CVE-2025-27238 | LOW | 2.1 | Sep 12, 2025 | Due to a bug in Zabbix API, the hostprototype.get method lists all host prototypes to users that do not have any user groups assigned to them. |
| CVE-2024-42325 | LOW | 2.1 | Apr 2, 2025 | Zabbix API user.get returns all users that share common group with the calling user. This includes media and other information, such as login attempts, etc. |