Quick answers
- Is CVE-2026-59783 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59783 being exploited in the wild.
- How severe is CVE-2026-59783?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Zabbix Proxy 7.0.0–7.0.28, 7.4.0–7.4.12; Zabbix Server 7.0.0–7.0.28, 7.4.0–7.4.12.
- Is there a fix for CVE-2026-59783?
- Yes: fixed in Zabbix Server 7.0.29, 7.4.13; Zabbix Proxy 7.0.29, 7.4.13. Until then: Disable item data collection for any binary items with untrusted input until updating to a fixed version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59783 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-59783?
- Check whether you run Zabbix Proxy or Zabbix Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Zabbix Server 7.0.29, 7.4.13; Zabbix Proxy 7.0.29, 7.4.13
Disable item data collection for any binary items with untrusted input until updating to a fixed version.
Technical details
A denial-of-service vulnerability in Zabbix Server and Proxy binary item processing allows an authenticated attacker with trapper access to send malicious null-byte-containing data that triggers a crash. The vulnerability is specific to MySQL/MariaDB database backends and results in availability loss. Fixes are available in versions 7.0.29 and 7.4.13.
Affected products
- Zabbix Server 7.0.0–7.0.28, 7.4.0–7.4.12
- Zabbix Proxy 7.0.0–7.0.28, 7.4.0–7.4.12
Timeline
- 2026-10-05: disclosed