Vulnerabilities (CVE)

Filtered by vendor Zabbix Subscribe
Total 123 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2026-23923 1 Zabbix 1 Zabbix 2026-09-10 N/A 5.3 MEDIUM
An unauthenticated attacker can exploit the Frontend 'validate' action to blindly instantiate arbitrary PHP classes. The impact depends on environment setup but appears limited at this time.
CVE-2026-23920 1 Zabbix 1 Zabbix 2026-09-10 N/A 8.8 HIGH
Host and event action script input is validated with a regex (set by the administrator), but the validation runs in multiline mode. If ^ and $ anchors are used in user input validation, an injected newline lets authenticated users bypass the check and inject shell commands.
CVE-2026-23921 1 Zabbix 1 Zabbix 2026-09-10 N/A 8.8 HIGH
A low privilege Zabbix user with API access can exploit a blind SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL selects via the sortfield parameter. Although query results are not returned directly, an attacker can exfiltrate arbitrary database data through time-based techniques, potentially leading to session identifier disclosure and administrator account compromise.
CVE-2026-1199 1 Zabbix 1 Zabbix 2026-09-08 N/A 3.7 LOW
Zabbix API and Frontend login lockout mechanism has a flaw where several unsuccessful login requests are not properly counted towards the block counter if sent simultaneously, potentially allowing for more password guesses than intended.
CVE-2026-23922 1 Zabbix 1 Zabbix 2026-09-08 N/A 4.9 MEDIUM
The email media OAuth field 'Client secret' cannot be read after saving, but a Super Admin can leak it by setting a malicious 'Token endpoint'. Changes were made to reset the client secret upon changing the token endpoint.
CVE-2026-23929 1 Zabbix 1 Zabbix 2026-09-08 N/A 5.4 MEDIUM
Prototype pollution vulnerability in searchParamsToObject() is leading to a persistent XSS in Maps. URL parameter processing was not filtering dangerous properties like __proto__, combined with jQuery's unsafe element creation that traversed the prototype chain.
CVE-2026-23930 1 Zabbix 1 Zabbix 2026-09-08 N/A 7.5 HIGH
An unauthenticated user is able to cause disproportionate CPU load on the Frontend webserver by sending specifically crafted requests to the Frontend popup.testtriggerexpr action, leading to potential denial of service.
CVE-2026-23925 1 Zabbix 1 Zabbix 2026-06-17 N/A 8.1 HIGH
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 1 Zabbix 1 Frontend 2026-06-17 N/A 6.5 MEDIUM
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-49641 1 Zabbix 1 Zabbix 2026-06-17 N/A 4.3 MEDIUM
A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.view.refresh action and therefore still retrieve a list of active problems.
CVE-2025-27240 1 Zabbix 1 Zabbix 2026-06-17 N/A 7.2 HIGH
A Zabbix adminitrator can inject arbitrary SQL during the autoremoval of hosts by inserting malicious SQL in the 'Visible name' field.
CVE-2025-27238 1 Zabbix 1 Zabbix 2026-06-17 N/A 3.5 LOW
Due to a bug in Zabbix API, the hostprototype.get method lists all host prototypes to users that do not have any user groups assigned to them.
CVE-2025-27236 1 Zabbix 1 Zabbix 2026-06-17 N/A 6.5 MEDIUM
A regular Zabbix user can search other users in their user group via Zabbix API by select fields the user does not have access to view. This allows data-mining some field values the user does not have access to.
CVE-2025-27232 1 Zabbix 1 Frontend 2026-06-17 N/A 4.9 MEDIUM
An authenticated Zabbix Super Admin can exploit the oauth.authorize action to read arbitrary files from the webserver leading to potential confidentiality loss.
CVE-2025-27231 1 Zabbix 1 Zabbix 2026-06-17 N/A 4.9 MEDIUM
The LDAP 'Bind password' value cannot be read after saving, but a Super Admin account can leak it by changing LDAP 'Host' to a rogue LDAP server. To mitigate this, the 'Bind password' value is now reset on 'Host' change.
CVE-2024-45700 1 Zabbix 1 Zabbix 2026-06-17 N/A 6.5 MEDIUM
Zabbix server is vulnerable to a DoS vulnerability due to uncontrolled resource exhaustion. An attacker can send specially crafted requests to the server, which will cause the server to allocate an excessive amount of memory and perform CPU-intensive decompression operations, ultimately leading to a service crash.
CVE-2024-45699 1 Zabbix 1 Zabbix 2026-06-17 N/A 5.4 MEDIUM
The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.
CVE-2024-42333 1 Zabbix 1 Zabbix 2026-06-17 N/A 2.7 LOW
The researcher is showing that it is possible to leak a small amount of Zabbix Server memory using an out of bounds read in src/libs/zbxmedia/email.c
CVE-2024-42332 1 Zabbix 1 Zabbix 2026-06-17 N/A 3.7 LOW
The researcher is showing that due to the way the SNMP trap log is parsed, an attacker can craft an SNMP trap with additional lines of information and have forged data show in the Zabbix UI. This attack requires SNMP auth to be off and/or the attacker to know the community/auth details. The attack requires an SNMP item to be configured as text on the target host.
CVE-2024-42331 1 Zabbix 1 Zabbix 2026-06-17 N/A 3.3 LOW
In the src/libs/zbxembed/browser.c file, the es_browser_ctor method retrieves a heap pointer from the Duktape JavaScript engine. This heap pointer is subsequently utilized by the browser_push_error method in the src/libs/zbxembed/browser_error.c file. A use-after-free bug can occur at this stage if the wd->browser heap pointer is freed by garbage collection.