CVE-2025-14740: Docker Desktop Privilege Escalation Flaw

CVE-2025-14740 Overview

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, enabling two distinct exploitation scenarios that can lead to arbitrary code execution.

In the first scenario (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. 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.

In the second scenario (TOCTOU Attack), during installation there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates the directory and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files with attacker-controlled ACLs during this window, achieving the same code execution outcome.

Critical Impact
Local privilege escalation and arbitrary code execution through improper directory permission handling during Docker Desktop installation on Windows systems.

Affected Products

Docker Desktop for Windows (versions prior to security patch)
Windows systems with Docker Desktop installations
Environments where low-privileged users can create directories in C:\ProgramData

Discovery Timeline

2026-02-04 - CVE CVE-2025-14740 published to NVD
2026-02-04 - Last updated in NVD database

Technical Details for CVE-2025-14740

Vulnerability Analysis

This vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) stems from fundamental flaws in how the Docker Desktop installer manages directory creation and permission assignment on Windows systems. The core issue is that the installer fails to verify ownership of the target directory before proceeding with installation, and introduces a race condition during the ACL application process.

The attack surface is local, requiring the attacker to have low-privileged access to the target system. However, the impact is significant as successful exploitation results in high confidentiality, integrity, and availability impact due to the ability to execute arbitrary code in the context of users running Docker Desktop.

Root Cause

The root cause lies in two distinct security failures within the Docker Desktop Windows installer:

Ownership Verification Gap: The installer does not check whether C:\ProgramData\DockerDesktop was pre-created by another user before installation. When the directory already exists with attacker-controlled ownership, applying restrictive ACLs does not revoke the owner's ability to modify those ACLs later.
Race Condition Window: There exists a temporal gap between directory creation and ACL application during the installation process. This TOCTOU vulnerability allows an attacker monitoring file system operations to inject malicious content before permissions are locked down.

Both issues allow manipulation of the install-settings.json configuration file, specifically the credentialHelper setting, which can be redirected to execute attacker-controlled code.

Attack Vector

The attack requires local access to the Windows system where Docker Desktop will be installed or is being installed. For the persistent attack scenario, the attacker must pre-create the target directory before any installation attempt. For the TOCTOU attack, the attacker must actively monitor file system operations during installation.

The exploitation mechanism involves modifying the install-settings.json file to specify a malicious credentialHelper binary. When Docker Desktop is subsequently launched by any user, the malicious credential helper executes with that user's privileges. This attack is particularly dangerous in multi-user environments or systems where administrators install software for end users.

For detailed technical information on these vulnerabilities, refer to the Zero Day Initiative Advisory ZDI-CAN-28190 and Zero Day Initiative Advisory ZDI-CAN-28542.

Detection Methods for CVE-2025-14740

Indicators of Compromise

Unexpected ownership of C:\ProgramData\DockerDesktop by non-administrative users
Modification of install-settings.json after initial installation
Unusual credentialHelper paths pointing to non-standard locations
File system audit events showing ACL modifications on Docker Desktop directories

Detection Strategies

Monitor for directory creation events in C:\ProgramData by non-administrative accounts prior to software installations
Implement file integrity monitoring on Docker Desktop configuration files, particularly install-settings.json
Audit ownership and ACL changes on C:\ProgramData\DockerDesktop and its subdirectories
Deploy endpoint detection for suspicious process execution chains originating from Docker Desktop credential helper invocations

Monitoring Recommendations

Enable Windows Security Auditing for object access events on the C:\ProgramData\DockerDesktop directory
Configure SIEM alerts for ACL modification events by non-administrative users on installation directories
Implement real-time monitoring for unexpected binary execution through Docker credential helper mechanisms
Review Docker Desktop installations for proper directory ownership as part of security baseline assessments

How to Mitigate CVE-2025-14740

Immediate Actions Required

Verify ownership of C:\ProgramData\DockerDesktop is held by appropriate system accounts (SYSTEM or Administrators)
Review and correct ACLs on Docker Desktop installation directories to ensure only authorized users have write access
Check install-settings.json for any unauthorized credentialHelper configurations
Consider uninstalling and reinstalling Docker Desktop after manually removing the pre-existing directory structure

Patch Information

Consult the Docker Security Documentation for the latest security updates and patched versions. Organizations should upgrade to the latest version of Docker Desktop that addresses these permission assignment vulnerabilities.

The Zero Day Initiative has published advisories ZDI-CAN-28190 and ZDI-CAN-28542 with additional details on affected versions and remediation guidance.

Workarounds

Pre-create C:\ProgramData\DockerDesktop with proper SYSTEM/Administrators ownership before Docker Desktop installation
Restrict low-privileged user access to create directories in C:\ProgramData through Group Policy
Implement application whitelisting to prevent execution of unauthorized binaries specified as credential helpers
Deploy endpoint protection solutions to monitor and block suspicious file system operations during software installation

bash

# Windows PowerShell: Verify directory ownership and reset if compromised
# Check current ownership
Get-Acl "C:\ProgramData\DockerDesktop" | Select-Object Owner

# Reset ownership to Administrators (run as Administrator)
$acl = Get-Acl "C:\ProgramData\DockerDesktop"
$owner = New-Object System.Security.Principal.NTAccount("BUILTIN\Administrators")
$acl.SetOwner($owner)
Set-Acl "C:\ProgramData\DockerDesktop" $acl