| CVE ID |
CVE-2026-23933 |
| CVSS score |
7.7 (High) |
| CVSS vector |
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| Affected components |
Frontend, Server |
| Summary |
Hardcoded session key in Zabbix 7.4 |
| Description |
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. |
| Known attack vectors |
An unauthenticated attacker with Frontend access might be able to generate valid session cookies in certain deployments. |
| Affected and fix version/s |
Affected: 7.4.0 - 7.4.10 → Fixed: 7.4.11 |
| Mitigation |
Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB. |
| Workarounds |
As a workaround, the pre-seeded session key can be manually cleared from Zabbix DB by setting value of 'settings.session_key' to an empty string. Zabbix Frontend will then generate a new random key. |
| Acknowledgements |
Zabbix wants to thank Daniel Shemesh and Or Ida for submitting this report on the HackerOne bug bounty platform. |
Defect (Security)
Major