Which versions of Docker are affected by EUVD-2026-14958?

CVE-2026-23924 presents moderate security risk rated CVSS 6.1. Exploitation could compromise the security of affected deployments.

How to fix or mitigate EUVD-2026-14958?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Docker EUVD-2026-14958

Q: What is the CVSS score of EUVD-2026-14958?

EUVD-2026-14958 has a CVSS 4.0 base score of 6.1 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

| CVE-2026-23924 MEDIUM

Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (CWE-88)

2026-03-24 Zabbix

GHSA-xfvx-fm25-g3v4

Docker Code Injection

6.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Lifecycle Timeline

EUVD ID Assigned

Mar 24, 2026 - 19:00 euvd

EUVD-2026-14958

Analysis Generated

Mar 24, 2026 - 19:00 vuln.today

CVE Published

Mar 24, 2026 - 18:30 nvd

MEDIUM 6.1

DescriptionCVE.org

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.

AnalysisAI

The Zabbix Agent 2 Docker plugin contains an argument injection vulnerability in the 'docker.container_info' parameter handler that fails to properly sanitize user-supplied input before forwarding requests to the Docker daemon. An authenticated attacker who can invoke Agent 2 can exploit this flaw to read arbitrary files from running Docker containers by injecting malicious parameters through the Docker archive API, potentially exposing sensitive application data, credentials, and configuration files. While no CVSS score or EPSS data is currently available, and no indication of active exploitation in the wild has been reported, this represents a direct path to container escape and lateral movement for attackers with agent-level access.

Technical ContextAI

Zabbix Agent 2 (cpe:2.3:a:zabbix:zabbix) includes a Docker monitoring plugin that communicates with the Docker daemon API to collect container metrics and metadata. The vulnerability stems from CWE-88 (Argument Injection) in the parameter handling logic for the 'docker.container_info' function. When this function constructs requests to the Docker API—specifically the archive endpoint used to retrieve files from containers—it does not properly escape or validate user-supplied parameters. This allows an attacker to inject additional Docker API parameters that modify the intended query, such as injecting path traversal sequences or alternative archive paths. The Docker daemon, receiving these malformed requests, executes them with the privileges of the Zabbix agent process, typically running with elevated rights for monitoring purposes.

RemediationAI

Immediately apply the security patch released by Zabbix for CVE-2026-23924, available through the Zabbix support portal at https://support.zabbix.com/browse/ZBX-27642. Upgrade to the patched version of Zabbix Agent 2 once available. As an interim mitigation, restrict network and local access to Agent 2 listening ports to only trusted Zabbix server instances and administrative users; disable or isolate the Docker plugin if it is not actively required for monitoring. Additionally, review and audit which containers and hosts have the Zabbix agent deployed with Docker plugin enabled, and restrict the agent's Docker API socket permissions to the minimum necessary user/group. Monitor Zabbix agent logs for suspicious docker.container_info invocations with unusual parameters.