Zabbix vulnerabilities
Published CVEs affecting Zabbix products: 31 record(s), with severity, exploitation and fixes.
CVE-2026-23925
High · 8.1
CWE-863 Mar 6, 2026
Unauthorized host creation via configuration.import API by low-privilege user with write permissions
An authenticated Zabbix user (User role) with template/host write permissions is able to create objects via the configuration.import API. This can lead to confidentiality loss by creating unauthorized hosts. Note that the User role is normally not sufficient to create and edit templates/hosts even with write permissions.
CVE-2025-49643
Medium · 6.5
CWE-405 Dec 1, 2025
Frontend DoS vulnerability due to asymmetric resource consumption
An authenticated Zabbix user (including Guest) is able to cause disproportionate CPU load on the webserver by sending specially crafted parameters to /imgstore.php, leading to potential denial of service.
CVE-2025-49642
Medium · 5.9
CWE-426 Dec 1, 2025
Agent builds for AIX vulnerable to library loading hijacking
Library loading on AIX Zabbix Agent builds can be hijacked by local users with write access to the /home/cecuser directory.
CVE-2025-27232
Medium · 4.9
CWE-918 Dec 1, 2025
Frontend arbitrary file read in oauth.authorize action
An authenticated Zabbix Super Admin can exploit the oauth.authorize action to read arbitrary files from the webserver leading to potential confidentiality loss.
CVE-2022-23134
Medium · 5.3
KEV High · 63 Public exploit CWE-287 Jan 13, 2022
Zabbix Frontend Improper Access Control Vulnerability
After the initial setup process, some steps of setup.php file are reachable not only by super-administrators, but by unauthenticated users as well. Malicious actor can pass step checks and potentially change the configuration of Zabbix Frontend.
CVE-2022-23131
Critical · 9.8
KEV Urgent · 73 Public exploit CWE-290 Jan 13, 2022
Zabbix Frontend Authentication Bypass Vulnerability
In the case of instances where the SAML SSO authentication is enabled (non-default), session data can be modified by a malicious actor, because a user login stored in the session was not verified. Malicious unauthenticated actor may exploit this issue to escalate privileges and gain admin access to Zabbix Frontend. To perform the attack, SAML authentication is required to be enabled and the actor has to know the username of Zabbix user (or use the guest account, which is disabled by default).