Scenario 1 (Persistent Attack):
If a low-privileged attacker pre-creates C:\ProgramData\DockerDesktop before Docker Desktop installation, the attacker retains ownership of the directory even after the installer applies restrictive ACLs. At any time after installation completes, the attacker can modify the directory ACL (as the owner) and tamper with critical configuration files such as install-settings.json to specify a malicious credentialHelper, causing arbitrary code execution when any user runs Docker Desktop.
Scenario 2 (TOCTOU Attack):
During installation, there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates C:\ProgramData\DockerDesktop and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files (such as install-settings.json) with attacker-controlled ACLs during this window, achieving the same code execution outcome.
Project Subscriptions
No data.
No advisories yet.
Solution
Docker has implemented the following mitigations: - Atomic creation of C:\ProgramData\DockerDesktop with admin ownership and correct ACLs - Verification that directory is owned by known admin SIDs (SYSTEM or Administrators) - Installation aborts if directory is not owned by trusted elevated SID - TOCTOU protection through atomic operations setting ownership and ACLs simultaneously Update to Docker Desktop version 4.56 or later.
Workaround
No workaround given by the vendor.
Wed, 04 Feb 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer's handling of the C:\ProgramData\DockerDesktop directory. The installer creates this directory without proper ownership verification, creating two exploitation scenarios: Scenario 1 (Persistent Attack): If a low-privileged attacker pre-creates C:\ProgramData\DockerDesktop before Docker Desktop installation, the attacker retains ownership of the directory even after the installer applies restrictive ACLs. At any time after installation completes, the attacker can modify the directory ACL (as the owner) and tamper with critical configuration files such as install-settings.json to specify a malicious credentialHelper, causing arbitrary code execution when any user runs Docker Desktop. Scenario 2 (TOCTOU Attack): During installation, there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates C:\ProgramData\DockerDesktop and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files (such as install-settings.json) with attacker-controlled ACLs during this window, achieving the same code execution outcome. | |
| Title | Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities | |
| Weaknesses | CWE-732 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Docker
Published:
Updated: 2026-02-04T13:57:23.002Z
Reserved: 2025-12-15T18:58:24.043Z
Link: CVE-2025-14740
No data.
Status : Awaiting Analysis
Published: 2026-02-04T14:16:08.533
Modified: 2026-02-04T16:33:44.537
Link: CVE-2025-14740
No data.
OpenCVE Enrichment
No data.