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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Zabbix | Zabbix | — | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | zabbix | No fix yet | — |
| Ubuntu 26.04 LTS | zabbix | No fix yet | — |
Show 5 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 22.04 LTS | zabbix | No fix yet | — |
| Ubuntu Pro 20.04 LTS | zabbix | No fix yet | — |
| Ubuntu Pro 18.04 LTS | zabbix | No fix yet | — |
| Ubuntu Pro 16.04 LTS | zabbix | No fix yet | — |
| Ubuntu Pro 14.04 LTS | zabbix | No fix yet | — |
Advisories 2
- NCSC-2026-0320 Kwetsbaarheden verholpen in Zabbix NCSC-NL (Netherlands) · Aug 20, 2026
- WID-SEC-2026-2916 Zabbix: Mehrere Schwachstellen BSI CERT-Bund (WID) · Aug 18, 2026