- Top reward
- $3,000
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 60
- Last change
At a glance
What to know before you start testing.
- Pays up to $3,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$3,000 |
| High |
|
$1,500 |
| Medium |
|
$500 |
| Low |
|
$200 |
Scope
1 asset you may test, 10 excluded.
Source code 1
- https://www.zabbix.com/download_sources No bounty
Out of scope (10)
- https://academy.zabbix.com
- https://blog.zabbix.com
- https://cloud.zabbix.com
- https://exam.zabbix.com
- https://git.zabbix.com
- https://shop.zabbix.com
- https://space.zabbix.com
- https://support.zabbix.com
- https://translate.zabbix.com
- https://www.zabbix.com
Changes
Tracked since 12 Nov 2026. Last checked 43 minutes ago.
-
Paused
Paused. Not accepting reports right now.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Status
Program status changed
-
Rules updated
The program rules were edited
-
Rules updated
Added: “Scope of DoS issues”
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-59781 | When Zabbix Agent was installed on Windows into a custom installation directory, the installer did not verify whether the selected directory had secure access permissions. If the target directory allowed unauthorized users to modify its contents, an attacker could place a malicious DLL that could later be loaded by the application, resulting in DLL sideloading. The installer has been hardened to d | Medium 5.4 | 18 Aug 2026 |
| CVE-2026-23933 | 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 ha | High 7.7 | 18 Aug 2026 |
| CVE-2026-23934 | An authenticated user is able to cause disproportionate CPU load on the Frontend webserver by sending specifically crafted requests to the Frontend validate.api.exists action, leading to potential denial of service. | Medium 5.1 | 18 Aug 2026 |
| CVE-2026-23935 | A Zabbix administrator is able to read out of bounds memory by utilizing a flaw in script item/preprocessing (JavaScript) HttpRequest logic, leading to potential confidentiality loss. | Medium 6.8 | 18 Aug 2026 |
| CVE-2026-23937 | The Zabbix API host.get action can be exploited by authenticated users to extract a host's PSK key leading to potential loss of data integrity. | Medium 6.0 | 18 Aug 2026 |
| CVE-2026-23938 | An authenticated administrator is able to crash Zabbix server or proxy by creating specifically crafted preprocessing/script item JavaScript scripts, leading to potential denial of service. | Low 2.1 | 18 Aug 2026 |
| CVE-2026-1199 | 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. | Medium 6.9 | 18 Aug 2026 |
| CVE-2026-23922 | 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. | Low 2.1 | 18 Aug 2026 |
| CVE-2026-23929 | 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. | High 8.5 | 18 Aug 2026 |
| CVE-2026-23930 | 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. | Medium 5.3 | 18 Aug 2026 |
| CVE-2026-23931 | The frontend validatate.api.exists action can be exploited by authenticated users to extract plaintext user macro values leading to potential loss of confidentiality. | Medium 5.3 | 18 Aug 2026 |
| CVE-2026-23927 | A user able to connect to Agent 2 can inject an Oracle TNS connection string via the 'service' parameter. This can lead to Agent 2 connecting to an attacker-controlled server and leaking Oracle database credentials if they are saved in a named session. | Medium 5.1 | 6 May 2026 |
| CVE-2026-23928 | The Item history widget (in Zabbix 7.0+) or the Plain text widget (in Zabbix 6.0) can execute injected JavaScript when HTML display is enabled. This can allow an attacker to perform unauthorized actions depending on which user opens a dashboard containing these widgets. The malicious JavaScript would have to come from a monitored host controlled by the attacker. Note: the Item history widget is a | High 7.3 | 6 May 2026 |
| CVE-2026-23926 | An authenticated (non-super) administrator can create a maintenance period with a JavaScript payload that is executed by any user that opens tooltip for that maintenance period in the Host navigator widget. This can allow the attacker to perform unauthorized actions depending on which user opens the tooltip. | High 7.3 | 6 May 2026 |
| CVE-2026-23921 | 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 acco | High 8.7 | 24 Mar 2026 |
| CVE-2026-23923 | 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. | Medium 6.9 | 24 Mar 2026 |
| CVE-2026-23924 | Zabbix Agent 2 Docker plugin does not properly sanitize the 'docker.container_info' parameters when forwarding them to the Docker daemon. An attacker capable of invoking Agent 2 can read arbitrary files from running Docker containers by injecting them via the Docker archive API. | Medium 6.1 | 24 Mar 2026 |
| CVE-2026-23920 | 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. | High 7.7 | 24 Mar 2026 |
| CVE-2026-23919 | For performance reasons Zabbix Server/Proxy reuses JavaScript (Duktape) contexts (used in script items, JavaScript reprocessing, Webhooks). This can lead to confidentiality loss where a regular (non-super) Zabbix administrator leaks data for hosts they do not have access to. A fix has been released that makes the built in Zabbix JavaScript objects read-only, but please be advised that usage of glo | High 7.1 | 24 Mar 2026 |
| 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. | Medium 5.1 | 6 Mar 2026 |
| 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. | Medium 6.0 | 1 Dec 2025 |
| 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. | Medium 6.8 | 1 Dec 2025 |
| 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. | Medium 4.3 | 3 Oct 2025 |
| 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. | Low 2.1 | 3 Oct 2025 |
| 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. | Medium 5.1 | 3 Oct 2025 |
| 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. | Low 2.1 | 12 Sep 2025 |
| CVE-2025-27240 | A Zabbix adminitrator can inject arbitrary SQL during the autoremoval of hosts by inserting malicious SQL in the 'Visible name' field. | High 7.5 | 12 Sep 2025 |
| 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. | Medium 6.0 | 2 Apr 2025 |
| 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. | Low 2.1 | 2 Apr 2025 |
| 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. | High 7.5 | 2 Apr 2025 |
| CVE-2024-36469 | Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one. | Low 2.3 | 2 Apr 2025 |
| 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. | High 8.6 | 2 Apr 2025 |
| 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. | High 8.8 | 28 Nov 2024 |
| 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. | Low 2.7 | 27 Nov 2024 |
| CVE-2024-42326 | There was discovered a use after free bug in browser.c in the es_browser_get_variant function | Medium 4.4 | 27 Nov 2024 |
| CVE-2024-42327 | 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. | Critical 9.9 | 27 Nov 2024 |
| CVE-2024-42328 | 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. | Low 3.3 | 27 Nov 2024 |
| 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. | Low 3.3 | 27 Nov 2024 |
| 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. | Critical 9.1 | 27 Nov 2024 |
| 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. | Low 3.3 | 27 Nov 2024 |
| 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. | Low 3.7 | 27 Nov 2024 |
| 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 | Low 2.7 | 27 Nov 2024 |
| CVE-2024-36468 | 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. | Low 3.0 | 27 Nov 2024 |
| CVE-2024-36467 | An authenticated user with API access (e.g.: user with default User role), more specifically a user with access to the user.update API endpoint is enough to be able to add themselves to any group (e.g.: Zabbix Administrators), except to groups that are disabled or having restricted GUI access. | High 7.5 | 27 Nov 2024 |
| CVE-2024-22117 | When a URL is added to the map element, it is recorded in the database with sequential IDs. Upon adding a new URL, the system retrieves the last sysmapelementurlid value and increments it by one. However, an issue arises when a user manually changes the sysmapelementurlid value by adding sysmapelementurlid + 1. This action prevents others from adding URLs to the map element. | Low 2.2 | 26 Nov 2024 |
| CVE-2024-36463 | The implementation of atob in "Zabbix JS" allows to create a string with arbitrary content and use it to access internal properties of objects. | Medium 6.5 | 26 Nov 2024 |
| CVE-2024-36460 | The front-end audit log allows viewing of unprotected plaintext passwords, where the passwords are displayed in plain text. | High 8.1 | 12 Aug 2024 |
| CVE-2024-36461 | Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine. | Critical 9.1 | 12 Aug 2024 |
| CVE-2024-36462 | Uncontrolled resource consumption refers to a software vulnerability where a attacker or system uses excessive resources, such as CPU, memory, or network bandwidth, without proper limitations or controls. This can cause a denial-of-service (DoS) attack or degrade the performance of the affected system. | High 7.5 | 12 Aug 2024 |
| CVE-2024-22123 | Setting SMS media allows to set GSM modem file. Later this file is used as Linux device. But due everything is a file for Linux, it is possible to set another file, e.g. log file and zabbix_server will try to communicate with it as modem. As a result, log file will be broken with AT commands and small part for log file content will be leaked to UI. | Low 2.7 | 12 Aug 2024 |
| CVE-2024-22114 | User with no permission to any of the Hosts can access and view host count & other statistics through System Information Widget in Global View Dashboard. | Medium 4.3 | 12 Aug 2024 |
| CVE-2024-22116 | An administrator with restricted permissions can exploit the script execution functionality within the Monitoring Hosts section. The lack of default escaping for script parameters enabled this user ability to execute arbitrary code via the Ping script, thereby compromising infrastructure. | Critical 9.9 | 12 Aug 2024 |
| CVE-2024-22121 | A non-admin user can change or remove important features within the Zabbix Agent application, thus impacting the integrity and availability of the application. | Medium 6.1 | 12 Aug 2024 |
| CVE-2024-22122 | Zabbix allows to configure SMS notifications. AT command injection occurs on "Zabbix Server" because there is no validation of "Number" field on Web nor on Zabbix server side. Attacker can run test of SMS providing specially crafted phone number and execute additional AT commands on modem. | Low 3.0 | 12 Aug 2024 |
| CVE-2024-22120 | Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection. | Critical 9.1 | 17 May 2024 |
| CVE-2024-22119 | The cause of vulnerability is improper validation of form input field “Name” on Graph page in Items section. | Medium 5.5 | 9 Feb 2024 |
| CVE-2023-32725 | The website configured in the URL widget will receive a session cookie when testing or executing scheduled reports. The received session cookie can then be used to access the frontend as the particular user. | Critical 9.6 | 18 Dec 2023 |
| CVE-2023-32726 | The vulnerability is caused by improper check for check if RDLENGTH does not overflow the buffer in response from DNS server. | Low 3.9 | 18 Dec 2023 |
| CVE-2023-32727 | An attacker who has the privilege to configure Zabbix items can use function icmpping() with additional malicious command inside it to execute arbitrary code on the current Zabbix server. | Medium 6.8 | 18 Dec 2023 |
| CVE-2023-32728 | The Zabbix Agent 2 item key smart.disk.get does not sanitize its parameters before passing them to a shell command resulting possible vulnerability for remote code execution. | Medium 4.6 | 18 Dec 2023 |