Quick answers
- Is CVE-2026-59788 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59788 being exploited in the wild.
- How severe is CVE-2026-59788?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Zabbix 7.4.0 through 7.4.11.
- Is there a fix for CVE-2026-59788?
- Yes: fixed in 7.4.12. Until then: Do not import media type configurations from untrusted sources until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59788 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-59788?
- Check whether you run Zabbix 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: 7.4.12
Do not import media type configurations from untrusted sources until upgrading.
Technical details
The OAuth form passes the Authorization endpoint URL directly to window.open() without validating the URL scheme, allowing javascript: URLs to be executed. The vulnerability is stored in the configuration and triggered when a Super Admin imports a crafted media type file and grants consent. An attacker with the ability to deliver the import file gains JavaScript execution in the context of the Super Admin's session.
Affected products
- Zabbix Zabbix 7.4.0 through 7.4.11
Timeline
- 2026-10-05: disclosed
- 2026-10-05: patched: Fixed in 7.4.12