CVE-2026-106581: 
Docker Desktop vulnerability analysis and mitigation

CVE-2026-106581 is a missing package signature verification vulnerability in Docker Desktop for Windows that allows a local attacker to execute arbitrary installer actions with LocalSystem privileges. All versions of Docker Desktop for Windows prior to 4.92.0 are affected. The vulnerability was published on October 9, 2026, and a patch was made available the same day. It carries a CVSS v4.0 base score of 7.3 (High) (GitHub Advisory, Feedly).

The root cause is classified as CWE-347 (Improper Verification of Cryptographic Signature): Docker Desktop Installer.exe did not verify the cryptographic signature of packages supplied via the install -package command-line argument. An attacker with low-level local access can craft a malicious package and pass it to the installer. Because the installer runs with elevated privileges after the user approves a Docker-signed UAC prompt, the attacker's package content executes as LocalSystem without any signature check blocking it. Exploitation requires the attacker to convince a user to approve the UAC prompt, which is the primary social engineering precondition (GitHub Advisory).

Successful exploitation grants the attacker code execution as LocalSystem — the highest privilege level on a Windows system — enabling full control over the affected host. This includes the ability to install malware, modify system files, create backdoor accounts, disable security controls, and pivot to other systems on the network. Confidentiality, integrity, and availability of both the vulnerable system and subsequent systems are all rated High (GitHub Advisory, Feedly).

As of the time of publication, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (Feedly). The EPSS score is approximately 0.075%, indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation is not automatable, as it requires active user interaction (UAC approval) and local access to deliver a crafted package.

1. Reconnaissance: Identify a target Windows machine running Docker Desktop version prior to 4.92.0, confirming the vulnerable installer is present (e.g., via Docker Desktop Installer.exe --version or checking installed software).
2. Craft malicious package: Prepare a crafted installer package containing attacker-controlled actions (e.g., a payload that drops a backdoor, creates a privileged user, or executes a reverse shell).
3. Deliver the package: Place the crafted package on the target system via any available means (e.g., phishing, shared network drive, malicious download, or direct local access).
4. Trigger the installer: Execute Docker Desktop Installer.exe install -package <path_to_crafted_package> on the target system, either directly or by tricking the user into running it.
5. Social engineering for UAC approval: The installer presents a Docker-signed UAC prompt; the attacker must convince the user to click "Yes" to approve elevation.
6. Achieve LocalSystem execution: Upon UAC approval, the installer processes the unsigned crafted package and executes the attacker-controlled actions as LocalSystem, granting full system control (GitHub Advisory).

• Process: Unexpected child processes spawned by Docker Desktop Installer.exe (e.g., cmd.exe, powershell.exe, net.exe) running under the SYSTEM account.
• Logs: Windows Security Event Log entries showing process creation (Event ID 4688) with Docker Desktop Installer.exe as the parent and unusual child processes; UAC elevation events (Event ID 4672) associated with the Docker installer.
• File System: Unexpected files dropped in system directories (e.g., C:\Windows\System32, C:\ProgramData) shortly after Docker installer execution; new or modified scheduled tasks or services created by the SYSTEM account.
• Network: Outbound connections from the SYSTEM account or Docker installer process to unknown external IP addresses following installer execution.

Docker has released Docker Desktop for Windows version 4.92.0, which adds signature verification for packages supplied to the installer, fully remediating this vulnerability. Users should upgrade to version 4.92.0 or later immediately. As a precautionary measure, users should exercise caution when approving UAC prompts and verify the legitimacy and source of any Docker Desktop installation packages before running them (GitHub Advisory, Docker Release Notes).

Initial community discussion was observed on Mastodon (infosec.exchange) shortly after disclosure, and the vulnerability was picked up by several CVE tracking and threat intelligence aggregation services. No major vendor statements beyond Docker's own release notes or notable independent researcher write-ups have been identified at this time (Feedly).