{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14740 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14740 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14740 is a medium-severity vulnerability in Docker Desktop, published on 4 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-14740 and fix it if it is affected.\n\nWhat it is: CVE-2025-14740 is a medium-severity vulnerability in Docker Desktop, published on 4 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-14740 in the wild and no public exploit code.\n\nAffected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-14740/ (Markdown: https://insights.sbomify.com/CVE-2025-14740/index.md)","id":"CVE-2025-14740","markdown":"https://insights.sbomify.com/CVE-2025-14740/index.md","name":"CVE-2025-14740","record":{"aliases":["GHSA-wqrh-gcr7-7hj3"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Desktop","requires_auth":"low_privilege","summary":"Low-privileged attackers can escalate privileges and execute arbitrary code by exploiting insecure directory permissions in Docker Desktop for Windows.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"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:\n\nScenario 1 (Persistent Attack):\nIf 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.\n\nScenario 2 (TOCTOU Attack):\nDuring 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities","id":"CVE-2025-14740","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in Frontend Admin by DynamiApps","id":"CVE-2025-14741"},"packages":[],"prev":{"headline":"Uninitialized Pointer Vulnerability in TP-Link WR940N and WR941ND","id":"CVE-2025-14739"},"products":["Docker Desktop"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Docker Inc."]},"summary":"Low-privileged attackers can escalate privileges and execute arbitrary code by exploiting insecure directory permissions in Docker Desktop for Windows.","url":"https://insights.sbomify.com/CVE-2025-14740/"}