Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-59788 Overview
CVE-2026-59788 is a stored cross-site scripting (XSS) vulnerability [CWE-79] in the Zabbix email media type OAuth configuration form. The form passes the Authorization endpoint value directly to window.open() without validating the URL scheme. An attacker who supplies a javascript: URL within a crafted media type configuration can execute arbitrary JavaScript in the browser context of a Super Admin who grants OAuth consent. The media type can be delivered as an import file, enabling abuse during configuration review workflows. Successful exploitation runs attacker-controlled script with the privileges of the authenticated Super Admin session.
Critical Impact
Arbitrary JavaScript execution in the browser of a Zabbix Super Admin granting OAuth consent, enabling session abuse and configuration tampering.
Affected Products
- Zabbix (email media type OAuth form) — see vendor issue tracker for affected versions
- Zabbix frontend components handling media type import
- Zabbix Super Admin console sessions
Discovery Timeline
- 2026-10-05 - CVE-2026-59788 published to the National Vulnerability Database
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-59788
Vulnerability Analysis
The flaw resides in client-side handling of the OAuth Authorization endpoint field in the Zabbix email media type configuration form. The frontend takes the user-controlled Authorization endpoint string and passes it to window.open() to initiate the OAuth consent flow. Because the code does not validate that the URL uses an http: or https: scheme, a javascript: URL is accepted and executed in the current document context.
Super Admins frequently import media type templates from third parties. When a Super Admin opens a crafted media type and clicks the OAuth consent button, the embedded javascript: payload executes under the admin's session. The payload can read tokens, call Zabbix API endpoints, modify configuration, or create persistence.
Root Cause
The root cause is missing input validation on a URL field that is subsequently used as a navigation target. The frontend treats the Authorization endpoint as a trusted URL and does not enforce an allowlist of safe schemes before invoking window.open(). This is a classic DOM-based XSS pattern mapped to [CWE-79].
Attack Vector
Exploitation requires an attacker to supply a malicious media type configuration, typically through an import file shared with or uploaded by a Super Admin. User interaction is required: the Super Admin must open the media type and trigger the OAuth consent action. The attack vector is network-reachable, authentication prerequisites are high (Super Admin consent), and no server-side code execution occurs directly, though downstream API abuse is possible.
No verified public exploit code is available. See the Zabbix Issue ZBX-28198 tracker for the authoritative technical description.
Detection Methods for CVE-2026-59788
Indicators of Compromise
- Media type configurations where the authorization_url or equivalent OAuth endpoint field begins with javascript: or any scheme other than https:
- Unexpected media type imports performed by Super Admin accounts outside of change windows
- Zabbix API activity originating from browser sessions immediately after opening a newly imported media type
Detection Strategies
- Audit Zabbix frontend audit logs for media type create or update events and inspect the Authorization endpoint value for non-HTTP schemes
- Review XML or YAML media type import files in version control and ticketing systems for javascript: strings in URL fields
- Correlate OAuth consent clicks by Super Admin accounts with subsequent anomalous Zabbix API calls such as user creation or script modification
Monitoring Recommendations
- Alert on any Super Admin session that performs media type import followed by immediate OAuth consent interaction
- Monitor browser Content Security Policy violation reports from the Zabbix frontend domain
- Log and review all configuration changes made within short windows after media type imports
How to Mitigate CVE-2026-59788
Immediate Actions Required
- Restrict Super Admin accounts and avoid importing media type configurations from untrusted sources
- Review existing media type definitions and remove any OAuth Authorization endpoints that do not use https:
- Apply the vendor patch referenced in Zabbix Issue ZBX-28198 once available for your branch
Patch Information
Refer to the Zabbix bug tracker entry ZBX-28198 for fixed version numbers and backport details. Apply the fix to all Zabbix frontend instances, including redundant and staging environments, and clear browser caches for admin workstations after upgrade.
Workarounds
- Enforce a strict Content Security Policy on the Zabbix frontend that disallows inline script and javascript: navigation
- Limit Super Admin role assignment and require peer review before importing any media type configuration file
- Pre-process media type import files with a validator that rejects URL fields not matching an ^https?:// pattern
# Example pre-import validation to reject javascript: URLs in media type XML
grep -Ei 'authorization_url>\s*javascript:' mediatype_import.xml \
&& echo "REJECTED: javascript: URL present" \
|| echo "OK: no javascript scheme detected"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

