Quick answers
- Is CVE-2026-59782 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59782 being exploited in the wild.
- How severe is CVE-2026-59782?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Zabbix Proxy 6.0.0-6.0.47, 7.0.0-7.0.28, 7.4.0-7.4.12; Zabbix Server 6.0.0-6.0.47, 7.0.0-7.0.28, 7.4.0-7.4.12.
- Is there a fix for CVE-2026-59782?
- Yes: fixed in Server and Proxy: 6.0.48, 7.0.29, 7.4.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59782 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59782?
- 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: Server and Proxy: 6.0.48, 7.0.29, 7.4.13
Technical details
The Duktape JavaScript engine in Zabbix Server and Proxy fails to properly isolate memory access in preprocessing rules. An attacker with limited administrator privileges can craft malicious JavaScript preprocessing rules that read raw heap memory, bypassing access controls and exposing data from preprocessors not assigned to them. This is a local privilege escalation requiring existing administrative credentials.
Affected products
- Zabbix Server 6.0.0-6.0.47, 7.0.0-7.0.28, 7.4.0-7.4.12
- Zabbix Proxy 6.0.0-6.0.47, 7.0.0-7.0.28, 7.4.0-7.4.12
Timeline
- 2026-10-05: disclosed