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.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

Upgrade Zabbix Server to the latest version, an upgrade patch will remove the session key from the DB.


Workaround

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.

History

Tue, 18 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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.
Title Hardcoded session key in Zabbix 7.4
Weaknesses CWE-259
References
Metrics cvssV4_0

{'score': 7.7, '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'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Zabbix

Published:

Updated: 2026-08-18T13:35:12.855Z

Reserved: 2026-01-19T14:03:13.686Z

Link: CVE-2026-23933

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T13:17:21.567

Modified: 2026-08-18T13:17:21.567

Link: CVE-2026-23933

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses