CVE-2026-23933: Hardcoded session key in Zabbix 7.4

Published Aug 18, 2026

Updated

In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.

Affected Software

1 affected component

Zabbix Zabbix=7.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Zabbix Server to a version that resolves this vulnerability.
Fixed in 7.4

Event History

Aug 18, 2026

CVE Published

via MITRE·12:18 PM

Data Sourced

via MITRE·12:18 PM

RemedyDescriptionWeakness

Frequently Asked Questions

Which deployments are known to be exposed?

Known exposure is limited to Zabbix 7.4 deployments that use both SAML authentication and guest users. Other Zabbix deployment configurations have no known impact from this issue.

What does exploitation require and what could it allow?

An attacker would need to use the hardcoded Frontend session-signing key to forge a session cookie. In the known scenario, a forged valid cookie could result in unauthorized access.