# CVE-2026-23922: Zabbix email media OAuth secret leak to Super Admin

Source: https://junglewise.ai/threats/cve-2026-23922-zabbix-email-media-oauth-secret-leak-to-super-admin  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-18. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-23922 · Severity: medium · CVSS 4.9 · Published 2026-08-18

Zabbix, a widely-used infrastructure monitoring platform, contains a vulnerability in its email notification OAuth configuration. A Super Administrator can leak the stored OAuth client secret by setting a malicious token endpoint URL, allowing potential credential theft. This vulnerability affects only users with Super Admin privileges but could enable unauthorized access to integrated email services.

Technologies: [Zabbix](https://junglewise.ai/threats/technologies/zabbix). Vendors: [Zabbix](https://junglewise.ai/threats/vendors/zabbix).

## Quick answers

**Is CVE-2026-23922 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-23922 being exploited in the wild.

**How severe is CVE-2026-23922?** Medium severity, with a CVSS score of 4.9, published 18 August 2026.

**Which products and versions are affected?** Zabbix 7.4.0 to 7.4.8.

**Is there a fix for CVE-2026-23922?** A patch was published on 2026-08-18: Fixed in version 7.4.9 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-23922 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-23922?** 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.

## Technical details

The vulnerability exists in Zabbix Frontend's OAuth configuration for email media. The 'Client secret' field is hidden after saving for security purposes, but it is not cleared when the 'Token endpoint' is modified. A Super Admin can exploit this by setting a malicious token endpoint that captures the client secret during the OAuth flow. The root cause is insufficient secret rotation logic—the secret should be cleared (forcing the user to re-enter it) whenever the token endpoint changes. The fix resets the client secret whenever the token endpoint value is modified, requiring explicit re-entry by the administrator.

## Affected products

- Zabbix Zabbix 7.4.0 to 7.4.8

## Timeline

- 2026-08-18: disclosed
- 2026-08-18: patched: Fixed in version 7.4.9

## References

- [https://support.zabbix.com/browse/ZBX-28067](https://support.zabbix.com/browse/ZBX-28067)

## Related threats

- [Zabbix stored XSS in OAuth configuration form](https://junglewise.ai/threats/cve-2026-59788-the-email-media-type-oauth-form-passes-the-authorization-endpoint)
- [Zabbix Frontend credential disclosure via search filtering](https://junglewise.ai/threats/cve-2026-59785-host-search-in-frontend-allows-filtering-by-fields-that-are-not)
- [Zabbix API PSK key extraction in host.get](https://junglewise.ai/threats/cve-2026-23937-zabbix-api-psk-key-extraction-in-host-get)
- [Zabbix Frontend denial of service via validate.api.exists](https://junglewise.ai/threats/cve-2026-23934-zabbix-frontend-denial-of-service-via-validate-api-exists)
- [Zabbix Frontend session key disclosure in database](https://junglewise.ai/threats/cve-2026-23933-zabbix-frontend-session-key-disclosure-in-database)