# CVE-2026-23933: Zabbix Frontend session key disclosure in database

Source: https://junglewise.ai/threats/cve-2026-23933-zabbix-frontend-session-key-disclosure-in-database  
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-23933 · Severity: critical · CVSS 9.1 · Published 2026-08-18

Zabbix 7.4 stores the cryptographic key used to sign web interface session cookies in the database, where it can be read by attackers. This allows unauthorized users to forge valid session cookies and gain administrative access to the monitoring platform. The vulnerability only affects deployments using both SAML authentication and guest user access.

Technologies: [Zabbix](https://junglewise.ai/threats/technologies/zabbix), [Zabbix Frontend](https://junglewise.ai/threats/technologies/frontend), [Zabbix Server](https://junglewise.ai/threats/technologies/zabbix-server). Vendors: [Zabbix](https://junglewise.ai/threats/vendors/zabbix).

## Quick answers

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

**How severe is CVE-2026-23933?** Critical severity, with a CVSS score of 9.1, published 18 August 2026.

**Which products and versions are affected?** Zabbix Frontend 7.4.0 to 7.4.10; Zabbix Server 7.4.0 to 7.4.10.

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

**How is CVE-2026-23933 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-23933?** Check whether you run Zabbix, Zabbix Frontend 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.

## Technical details

The vulnerability is a cryptographic key exposure flaw in Zabbix 7.4 where the session signing key is written to the database seed instead of being randomly generated per deployment. An unauthenticated attacker with network access to the Zabbix frontend can read this key from the database and use it to forge valid session cookies. Exploitation is most practical on deployments that enable both SAML authentication and guest user access. The affected versions are 7.4.0 through 7.4.10; the fix is available in 7.4.11 and later. Workaround: manually clear the 'settings.session_key' database value to force regeneration of a random key.

## Affected products

- Zabbix Zabbix Server 7.4.0 to 7.4.10
- Zabbix Zabbix Frontend 7.4.0 to 7.4.10

## Timeline

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

## References

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

## 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 SNMP trap receiver record injection in zabbix_trap_receiver.pl](https://junglewise.ai/threats/cve-2026-59787-the-perl-snmp-trap-receiver-script-shipped-with-zabbix-does-not)
- [Zabbix Server and Proxy active agent heartbeat TLS bypass](https://junglewise.ai/threats/cve-2026-59786-zabbix-server-and-proxy-accept-the-active-agent-heartbeat-message)
- [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 Server and Proxy denial of service via binary items](https://junglewise.ai/threats/cve-2026-59783-the-zabbix-server-proxy-has-a-vulnerability-where-binary-items)