CVE-2026-23919: For performance reasons Zabbix Server/Proxy reuses JavaScript (Duktape) contexts (used in script items, JavaScript reprocessing, Webhooks)
Source GCVE Database
Not known to be exploited · CVSS 6.0 Medium.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
AI-suggested
A fix has been released that makes built-in Zabbix JavaScript objects read-only, mitigating the vulnerability. Users should update to the fixed version as per the vendor's guidance. Additionally, avoid using global JavaScript variables in scripts or preprocessing to prevent potential data leakage. Check the official Zabbix documentation for the latest remediation details.
Description
Zabbix Server and Proxy reuse JavaScript (Duktape) contexts for performance, which can cause data leakage between users. Specifically, non-super administrators may access confidential data from hosts they are not authorized to view. A fix has been released that makes built-in JavaScript objects read-only, but global JavaScript variables remain risky and their use is discouraged.