Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14740: CWE-732 Incorrect Permission Assignment for Critical Resource in Docker Inc. Docker Desktop

0
Medium
VulnerabilityCVE-2025-14740cvecve-2025-14740cwe-732
Published: Wed Feb 04 2026 (02/04/2026, 13:57:23 UTC)
Source: CVE Database V5
Vendor/Project: Docker Inc.
Product: Docker Desktop

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.

AI-Powered Analysis

AILast updated: 02/04/2026, 14:29:43 UTC

Technical Analysis

CVE-2025-14740 is a vulnerability classified under CWE-732 (Incorrect Permission Assignment for Critical Resource) affecting Docker Desktop for Windows. The root cause lies in the installer's handling of the C:\ProgramData\DockerDesktop directory, which is created without proper ownership verification or secure ACL application. Two exploitation scenarios exist: (1) Persistent Attack - a low-privileged attacker pre-creates the directory before installation, retaining ownership post-installation, allowing modification of critical configuration files like install-settings.json. By altering the credentialHelper setting, the attacker can achieve arbitrary code execution when Docker Desktop runs. (2) TOCTOU (Time-of-Check-Time-of-Use) Attack - during installation, a race condition allows an attacker monitoring the process to inject malicious files with attacker-controlled ACLs before secure permissions are set, resulting in similar code execution capabilities. The vulnerability requires local access with low privileges and some user interaction (installation execution). The CVSS v3.1 base score is 6.7 (medium), reflecting high impact on confidentiality, integrity, and availability but with higher attack complexity and required privileges. No patches or known exploits are currently reported, but the risk remains significant due to the potential for persistent code execution and system compromise.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the security of containerized development and deployment environments relying on Docker Desktop for Windows. Successful exploitation can lead to arbitrary code execution with the privileges of the Docker Desktop user, potentially allowing attackers to manipulate container configurations, steal sensitive data, or disrupt operations. Given Docker's widespread use in development, testing, and production workflows, compromise could cascade into broader network and application-level impacts. Persistent control over Docker Desktop configuration files could facilitate supply chain attacks or lateral movement within corporate networks. The requirement for local access limits remote exploitation but insider threats or compromised endpoints remain a concern. Organizations with regulatory obligations around data protection (e.g., GDPR) must consider the confidentiality implications of such breaches. The absence of known exploits in the wild provides a window for proactive mitigation.

Mitigation Recommendations

To mitigate CVE-2025-14740, European organizations should implement the following specific measures: 1) Ensure Docker Desktop installations are performed by trusted administrators on secure, monitored endpoints to prevent unauthorized pre-creation or tampering of the C:\ProgramData\DockerDesktop directory. 2) Employ endpoint protection solutions that detect and block unauthorized file system changes, especially during software installations. 3) Use application whitelisting and integrity monitoring to detect modifications to critical Docker configuration files such as install-settings.json. 4) Where possible, perform installations in controlled environments or with elevated privileges that prevent low-privileged users from interfering with installation directories. 5) Monitor installation logs and system events for suspicious activity indicative of TOCTOU exploitation attempts. 6) Advocate for and track vendor patches or updates addressing this vulnerability, applying them promptly once available. 7) Educate users and administrators about the risks of installing software from untrusted sources or under unsecure conditions. 8) Consider restricting Docker Desktop usage to dedicated machines with limited user access to reduce attack surface.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Docker
Date Reserved
2025-12-15T18:58:24.043Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983546df9fa50a62f8ff386

Added to database: 2/4/2026, 2:15:09 PM

Last enriched: 2/4/2026, 2:29:43 PM

Last updated: 2/6/2026, 11:29:00 PM

Views: 82

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats