{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23919 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23919 is a high-severity vulnerability in Zabbix Zabbix, published on 24 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23919 and fix it if it is affected.\n\nWhat it is: CVE-2026-23919 is a high-severity vulnerability in Zabbix Zabbix, published on 24 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23919 in the wild and no public exploit code.\n\nAffected product: Zabbix Zabbix. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-23919/ (Markdown: https://insights.sbomify.com/CVE-2026-23919/index.md)","id":"CVE-2026-23919","markdown":"https://insights.sbomify.com/CVE-2026-23919/index.md","name":"CVE-2026-23919","record":{"aliases":["DEBIAN-CVE-2026-23919","GHSA-h55g-ww3m-9hq9","UBUNTU-CVE-2026-23919"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zabbix monitoring server","requires_auth":"high_privilege","summary":"Insufficient isolation in Zabbix JavaScript contexts allows administrators to leak data from hosts they lack access to.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Zabbix","cpe":[{"product":"zabbix","vendor":"zabbix"}],"cvss":{"score":7.1,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"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 \u003ca href='https://www.zabbix.com/documentation/7.4/en/manual/installation/known_issues#preprocessing-global-variables-are-unsafe'\u003ein Zabbix documentation\u003c/a\u003e.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient isolation of JavaScript (Duktape) execution context on Zabbix Server","id":"CVE-2026-23919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"zabbix:zabbix","products":["zabbix:zabbix"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Zabbix","id":"CVE-2026-23920"},"packages":[],"prev":{"headline":"Apache HTTP Server: http2: double free and possible RCE on early reset","id":"CVE-2026-23918"},"products":["Zabbix"],"published":"2026-03-24","related":[{"cvss_score":9.1,"headline":"Zabbix Frontend Authentication Bypass","id":"CVE-2022-23131","kev_date_added":"2022-02-22","published":"2022-01-13"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-0640","kev_date_added":null,"published":"2007-01-31"},{"cvss_score":9.9,"headline":"SQL injection in user.get API","id":"CVE-2024-42327","kev_date_added":null,"published":"2024-11-27"},{"cvss_score":9.9,"headline":"Remote code execution within ping script","id":"CVE-2024-22116","kev_date_added":null,"published":"2024-08-09"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2013-3738","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2013-5743","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-10134","kev_date_added":null,"published":"2017-02-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["Zabbix"]},"summary":"Insufficient isolation in Zabbix JavaScript contexts allows administrators to leak data from hosts they lack access to.","url":"https://insights.sbomify.com/CVE-2026-23919/"}