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.
Published: 2026-08-18
Score: 7.7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In Zabbix 7.4 the key used to sign Frontend sessions is incorrectly stored in the database seed. The hard‑coded key can be extracted by an attacker who can then forge valid session cookies. When a deployment uses both SAML authentication and guest users this forgery permits unauthorized access to the web interface and may lead to privilege escalation, since the forged session is treated as a legitimate user session.

Affected Systems

All installations of Zabbix Server version 7.4 that have been configured with both SAML authentication and guest users are affected. The issue applies to the Zabbix product line as managed by the vendor Zabbix.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity, and the vulnerability is not currently listed in the CISA KEV catalog. The EPSS score is unavailable, so the current exploitation probability is unknown. Attackers would need to target a site with SAML authentication enabled and at least one guest account; upon obtaining the key from the database, they can craft a valid session cookie and impersonate a legitimate user. In the absence of these conditions the vulnerability has no known impact.

Generated by OpenCVE AI on August 18, 2026 at 13:50 UTC.

Remediation

Vendor Solution

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


Vendor 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.


OpenCVE Recommended Actions

  • Upgrade Zabbix Server to the latest version; the patch removes the hard‑coded session key from the database.
  • If an upgrade cannot be performed immediately, clear the pre‑seeded session key by setting the database field `settings.session_key` to an empty string; the frontend will generate a new random key.
  • Temporarily disable SAML authentication or prevent the use of guest users until the upgrade or key clearance has been applied.

Generated by OpenCVE AI on August 18, 2026 at 13:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 05:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


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

Type Values Removed Values Added
First Time appeared Zabbix
Zabbix zabbix
Vendors & Products Zabbix
Zabbix zabbix

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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Zabbix

Published:

Updated: 2026-08-19T03:55:57.404Z

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

Link: CVE-2026-23933

cve-icon Vulnrichment

Updated: 2026-08-18T12:51:57.299Z

cve-icon NVD

Status : Awaiting Analysis

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

Modified: 2026-09-01T20:56:59.203

Link: CVE-2026-23933

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T14:15:07Z

Weaknesses
  • CWE-259

    Use of Hard-coded Password