Docker Inc.Patching for Windows Mac Linux
CVE Vulnerabilities for Docker Desktop
| CVE | Published | Severity | Details | Exploitability | Impact | Vector |
|---|---|---|---|---|---|---|
| CVE‑2026‑6406 | 2026‑05‑22 19:17:05 | HIGH (9) | The Docker CLI --use-api-socket flag bypasses Enhanced Container Isolation (ECI) restrictions in Docker Desktop. When ECI is enabled, Docker socket mounts from containers are denied unless explicitly allowed via the admin-settings configuration. However, the --use-api-socket flag adds the Docker socket mount via the HostConfig.Mounts field rather than the HostConfig.Binds field. The ECI enforcement in the Docker Desktop API proxy only inspected Binds, allowing the mount to pass unchecked. This grants a container full access to the Docker Engine socket and, if the host user has logged in to container registries, their authentication credentials. A local attacker with the ability to run Docker CLI commands can exploit this to escape ECI restrictions, access the Docker Engine, and potentially escalate privileges. | 0 | 0 | LOCAL |
| CVE‑2026‑5843 | 2026‑05‑22 20:16:35 | HIGH (9) | The MLX inference backend in Docker Model Runner on macOS uses the MLX-LM library, which unconditionally imports and executes arbitrary Python files from model directories via the model_file configuration field in config.json. When a model's config.json specifies a model_file pointing to a Python file, MLX-LM uses importlib to load and execute it with no trust_remote_code gate or equivalent safety check. The MLX backend runs without sandboxing, resulting in arbitrary code execution on the Docker host as the Docker Desktop user. Any container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model from an attacker-controlled OCI registry and request inference. | 0 | 0 | LOCAL |
| CVE‑2026‑5817 | 2026‑05‑22 20:16:35 | HIGH (9) | The vllm-metal inference backend in Docker Model Runner on macOS unconditionally sets trust_remote_code=True when loading model tokenizers, and runs without sandboxing. This causes transformers.AutoTokenizer.from_pretrained() to import and execute arbitrary Python files included in any model pulled from an OCI registry, resulting in arbitrary code execution on the Docker host as the Docker Desktop user when inference is triggered. Any container on the Docker network can trigger this by calling the model-runner.docker.internal API to pull a malicious model and request inference. | 0 | 0 | LOCAL |
| CVE‑2025‑13743 | 2025‑12‑09 21:15:54 | LOW (2) | Docker Desktop diagnostics bundles were found to include expired Hub PATs in log output due to error object serialization. This poses a risk of leaking sensitive information in exported diagnostics, especially when access denied errors occurred. | 0 | 0 | LOCAL |
| CVE‑2023‑5166 | 2023‑09‑25 16:15:16 | HIGH (8) | Docker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL. This issue affects Docker Desktop: before 4.23.0. | 2 | 6 | NETWORK |
| CVE‑2023‑5165 | 2023‑09‑25 16:15:16 | HIGH (7) | Docker Desktop before 4.23.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions via the debug shell which remains accessible for a short time window after launching Docker Desktop. The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges. This issue has been fixed in Docker Desktop 4.23.0. Affected Docker Desktop versions: from 4.13.0 before 4.23.0. | 2 | 5 | LOCAL |
| CVE‑2023‑0633 | 2023‑09‑25 16:15:13 | HIGH (7) | In Docker Desktop on Windows before 4.12.0 an argument injection to installer may result in local privilege escalation (LPE).This issue affects Docker Desktop: before 4.12.0. | 1 | 6 | LOCAL |
| CVE‑2023‑0629 | 2023‑03‑13 12:15:11 | HIGH (7) | Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers without the additional hardening features provided by ECI. This would not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket). The affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges. This issue has been fixed in Docker Desktop 4.17.0. Affected Docker Desktop versions: from 4.13.0 before 4.17.0. | 2 | 5 | LOCAL |
| CVE‑2023‑0628 | 2023‑03‑13 12:15:11 | MEDIUM (6) | Docker Desktop before 4.17.0 allows an attacker to execute an arbitrary command inside a Dev Environments container during initialization by tricking a user to open a crafted malicious docker-desktop:// URL. | 2 | 4 | LOCAL |
| CVE‑2023‑0627 | 2023‑09‑25 16:15:13 | MEDIUM (7) | Docker Desktop 4.11.x allows --no-windows-containers flag bypass via IPC response spoofing which may lead to Local Privilege Escalation (LPE).This issue affects Docker Desktop: 4.11.X. | 1 | 5 | LOCAL |
| CVE‑2023‑0626 | 2023‑09‑25 16:15:13 | HIGH (8) | Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route. This issue affects Docker Desktop: before 4.12.0. | 2 | 6 | NETWORK |
| CVE‑2023‑0625 | 2023‑09‑25 16:15:13 | HIGH (8) | Docker Desktop before 4.12.0 is vulnerable to RCE via a crafted extension description or changelog. This issue affects Docker Desktop: before 4.12.0. | 2 | 6 | NETWORK |
| CVE‑2022‑26659 | 2022‑03‑25 21:15:09 | HIGH (7) | Docker Desktop installer on Windows in versions before 4.6.0 allows an attacker to overwrite any administrator writable files by creating a symlink in place of where the installer writes its log file. Starting from version 4.6.0, the Docker Desktop installer, when run elevated, will write its log files to a location not writable by non-administrator users. | 2 | 5 | LOCAL |
| CVE‑2022‑23774 | 2022‑02‑01 06:15:07 | MEDIUM (5) | Docker Desktop before 4.4.4 on Windows allows attackers to move arbitrary files. | 4 | 1 | NETWORK |
| CVE‑2021‑45449 | 2022‑01‑12 20:15:09 | MEDIUM (6) | Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files. | 2 | 4 | LOCAL |
| CVE‑2021‑44719 | 2022‑05‑25 16:15:08 | HIGH (8) | Docker Desktop 4.3.0 has Incorrect Access Control. | 2 | 6 | LOCAL |
| CVE‑2020‑15360 | 2020‑06‑27 13:15:10 | HIGH (8) | com.docker.vmnetd in Docker Desktop 2.3.0.3 allows privilege escalation because of a lack of client verification. | 2 | 6 | LOCAL |
| CVE‑2020‑11492 | 2020‑06‑05 14:15:11 | HIGH (8) | An issue was discovered in Docker Desktop through 2.2.0.5 on Windows. If a local attacker sets up their own named pipe prior to starting Docker with the same name, this attacker can intercept a connection attempt from Docker Service (which runs as SYSTEM), and then impersonate their privileges. | 2 | 6 | LOCAL |
Deep Windows, Mac, and Linux OS patching
Stay out of the "Negligent MSP" label because Lavawall® covers:- 30-312 times as many applications as popular RMMs.
- "optional" Windows patches, including firmware and drivers
- Mac OS and application patches
- Linux Kernel, OS, and package patches for more distribution types than we want to admit exist
Windows Mac Linux
What applications does Lavawall® monitor?
Lavawall monitors patches for over 7,500 applications. This is a summary of the most popular applications.Click here for the full list.
Click the applications below for the current version and known vulnerabilities.
Logos are property of their respective trademark holders and are not affiliated with ThreeShield or Lavawall. We have not audited the security of most of the listed tools.
The above listing includes products that Lavawall® monitors through public information and/or proprietary statistical analysis.
Although we do have a partner relationship with some of the listed products and companies, they do not necessarily endorse Lavawall® or have integrations with our systems.