CVE-2026-23927
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk14th percentile - higher than 14% of all known CVEs
Summary
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.
Risk Assessment
An attacker could capture Oracle database credentials, potentially leading to unauthorized data access. This could compromise data confidentiality and integrity.
Recommendation
Update Zabbix Agent 2 to a version containing the fix. Avoid saving credentials in named sessions and restrict access to Agent 2.
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-23924Medium
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.
Original NVD description (English source)
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.