-
Type:
Defect (Security)
-
Resolution: Fixed
-
Priority:
Major
-
None
-
Affects Version/s: None
-
Component/s: Proxy (P), Server (S)
-
None
| CVE ID | CVE-2026-23919 |
| CVSS score | 7.1 (High) |
| CVSS vector | CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L |
| Affected components | Server, Proxy |
| Summary | Insufficient isolation of JavaScript (Duktape) execution context on Zabbix Server |
| Description | 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 global JavaScript variables is not recommended because their content could be leaked. More information Zabbix documentation. |
| Known attack vectors | A regular Zabbix administrator (non-super) can overwrite some built in JavaScript functions that are then executed for other objects. Alternatively, a regular Zabbix administrator can read global JavaScript variables. |
| Affected and fix version/s | Affected: 6.0.0 - 6.0.40 → Fixed: 6.0.41 Affected: 7.0.0 - 7.0.18 → Fixed: 7.0.19 Affected: 7.2.0 - 7.2.12 → Fixed: 7.2.13 Affected: 7.4.0 - 7.4.2 → Fixed: 7.4.3 |
| Mitigation | Update the affected components to their respective fixed versions. Make sure JavaScript item preprocessing scripts don't store secret data in global variables. |
| Workarounds | - |
| Acknowledgements | Zabbix wants to thank Yerdan (big_john) for submitting this report on the HackerOne bug bounty platform. |