Filtered by vendor Zabbix
Subscribe
Total
135 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| 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-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. | |||||
| CVE-2024-42330 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 9.1 CRITICAL |
| The HttpRequest object allows to get the HTTP headers from the server's response after sending the request. The problem is that the returned strings are created directly from the data returned by the server and are not correctly encoded for JavaScript. This allows to create internal strings that can be used to access hidden properties of objects. | |||||
| CVE-2024-42329 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 3.3 LOW |
| The webdriver for the Browser object expects an error object to be initialized when the webdriver_session_query function fails. But this function can fail for various reasons without an error description and then the wd->error will be NULL and trying to read from it will result in a crash. | |||||
| CVE-2024-42328 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 3.3 LOW |
| When the webdriver for the Browser object downloads data from a HTTP server, the data pointer is set to NULL and is allocated only in curl_write_cb when receiving data. If the server's response is an empty document, then wd->data in the code below will remain NULL and an attempt to read from it will result in a crash. | |||||
| CVE-2024-42327 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 9.9 CRITICAL |
| A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API access can exploit this vulnerability. An SQLi exists in the CUser class in the addRelatedObjects function, this function is being called from the CUser.get function which is available for every user who has API access. | |||||
| CVE-2024-42326 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 4.4 MEDIUM |
| There was discovered a use after free bug in browser.c in the es_browser_get_variant function | |||||
| CVE-2024-42325 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 3.5 LOW |
| Zabbix API user.get returns all users that share common group with the calling user. This includes media and other information, such as login attempts, etc. | |||||
| CVE-2024-36469 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 3.1 LOW |
| Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one. | |||||
| CVE-2024-36468 | 1 Zabbix | 1 Zabbix | 2026-06-17 | N/A | 3.0 LOW |
| The reported vulnerability is a stack buffer overflow in the zbx_snmp_cache_handle_engineid function within the Zabbix server/proxy code. This issue occurs when copying data from session->securityEngineID to local_record.engineid without proper bounds checking. | |||||