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