彙總 Zabbix 相關全部產品的 CVE 與安全漏洞情報，包括 CVSS、EPSS、公開時間與漏洞情報資料。
歷史漏洞主要涉及 跨站腳本與輸入驗證問題 等問題，部分漏洞可能導致 記憶體損壞，並影響 生產負載與軟體部署 相關場景。
相關漏洞資料主要來源於公開漏洞披露與安全公告，可用於評估歷史漏洞暴露面與修補優先順序。
| CVE | 摘要 | 來源 | 最高 CVSS | EPSS % | 公開時間 | 更新時間 |
|---|---|---|---|---|---|---|
| CVE-2026-23925 | 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. | [email protected] | 5.1 | 0.26% | 2026-03-06 | 2026-06-17 |
| CVE-2025-49643 | 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. | [email protected] | 6.0 | 0.30% | 2025-12-01 | 2026-06-17 |
| CVE-2025-27232 | An authenticated Zabbix Super Admin can exploit the oauth.authorize action to read arbitrary files from the webserver leading to potential confidentiality loss. | [email protected] | 6.8 | 0.30% | 2025-12-01 | 2026-06-17 |
| CVE-2025-49641 | 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. | [email protected] | 5.1 | 0.27% | 2025-10-03 | 2026-06-17 |
| CVE-2025-27236 | 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. | [email protected] | 2.1 | 0.35% | 2025-10-03 | 2026-06-17 |
| CVE-2025-27231 | 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. | [email protected] | 4.3 | 0.38% | 2025-10-03 | 2026-06-17 |
| CVE-2025-27240 | A Zabbix adminitrator can inject arbitrary SQL during the autoremoval of hosts by inserting malicious SQL in the 'Visible name' field. | [email protected] | 7.5 | 1.19% | 2025-09-12 | 2026-06-17 |
| CVE-2025-27238 | 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. | [email protected] | 2.1 | 0.17% | 2025-09-12 | 2026-06-17 |
| CVE-2024-45700 | 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. | [email protected] | 6.0 | 0.32% | 2025-04-02 | 2026-06-17 |
| CVE-2024-45699 | 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. | [email protected] | 7.5 | 0.31% | 2025-04-02 | 2026-06-17 |
| CVE-2024-42325 | 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. | [email protected] | 2.1 | 0.30% | 2025-04-02 | 2026-06-17 |
| CVE-2024-36469 | Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one. | [email protected] | 2.3 | 0.29% | 2025-04-02 | 2026-06-17 |
| CVE-2024-36465 | A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter. | [email protected] | 8.6 | 29.26% | 2025-04-02 | 2026-06-17 |
| CVE-2024-36466 | A bug in the code allows an attacker to sign a forged zbx_session cookie, which then allows them to sign in with admin permissions. | [email protected] | 8.8 | 0.72% | 2024-11-28 | 2026-06-17 |
| CVE-2024-36464 | When exporting media types, the password is exported in the YAML in plain text. This appears to be a best practices type issue and may have no actual impact. The user would need to have permissions to access the media types and therefore would be expected to have access to these passwords. | [email protected] | 2.7 | 0.53% | 2024-11-27 | 2026-06-17 |
| CVE-2024-42333 | 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 | [email protected] | 2.7 | 0.60% | 2024-11-27 | 2026-06-17 |
| CVE-2024-42332 | 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. | [email protected] | 3.7 | 0.62% | 2024-11-27 | 2026-06-17 |
| CVE-2024-42331 | 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. | [email protected] | 3.3 | 0.26% | 2024-11-27 | 2026-06-17 |
| CVE-2024-42330 | 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. | [email protected] | 9.1 | 0.95% | 2024-11-27 | 2026-06-17 |
| CVE-2024-42329 | 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. | [email protected] | 3.3 | 0.24% | 2024-11-27 | 2026-06-17 |