CVE-2026-23924
MediumCVSS 4.9Exploitation Probability (EPSS)
Low risk17th percentile - higher than 17% of all known CVEs
Summary
The 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.
Risk Assessment
An attacker could access sensitive files inside Docker containers, potentially leading to data leakage or privilege escalation. This could compromise the confidentiality of data stored in containers.
Recommendation
Update Zabbix Agent 2 to a version containing the fix. Restrict access to Agent 2 to trusted users only and monitor for unusual Docker API requests.
Other vulnerabilities in Zabbix Agent 2
See all- CVE-2016-4338High
The MySQL user parameter configuration script in the Zabbix agent before version 2.0.18, 2.2.x before 2.2.13, and 3.0.x before 3.0.3, when used with a shell other than bash, allows attackers to execute arbitrary code or SQL commands via the mysql.size parameter.
- CVE-2026-59781Medium
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 detect potentially unsafe installation directories and now requires explicit user confirmation before proceeding with installation in such locations.
- CVE-2026-23927Medium
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.
Original NVD description (English source)
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.