CVE-2025-14740 (GCVE-0-2025-14740)
Vulnerability from cvelistv5 – Published: 2026-02-04 13:57 – Updated: 2026-02-05 04:55
VLAI?
Title
Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities
Summary
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.
Severity ?
6.7 (Medium)
CWE
- CWE-732 - Incorrect Permission Assignment for Critical Resource
Assigner
References
| URL | Tags | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Docker Inc. | Docker Desktop |
Affected:
0 , ≤ 4.56.0
(semver)
|
Credits
Nitesh Surana (niteshsurana.com) - Trend Micro Zero Day Initiative
Amol Dosanjh - Trend Micro Research
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-14740",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-04T00:00:00+00:00",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-02-05T04:55:14.212Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"platforms": [
"Windows"
],
"product": "Docker Desktop",
"vendor": "Docker Inc.",
"versions": [
{
"lessThanOrEqual": "4.56.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Nitesh Surana (niteshsurana.com) - Trend Micro Zero Day Initiative"
},
{
"lang": "en",
"type": "finder",
"value": "Amol Dosanjh - Trend Micro Research"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer\u0027s handling of the \u003ccode\u003eC:\\ProgramData\\DockerDesktop\u003c/code\u003e directory. The installer creates this directory without proper ownership verification, creating two exploitation scenarios:\u003cbr\u003e\u003cbr\u003e\u003cstrong\u003eScenario 1 (Persistent Attack)\u003c/strong\u003e:\nIf a low-privileged attacker pre-creates \u003ccode\u003eC:\\ProgramData\\DockerDesktop\u003c/code\u003e 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 \u003ccode\u003einstall-settings.json\u003c/code\u003e to specify a malicious \u003ccode\u003ecredentialHelper\u003c/code\u003e, causing arbitrary code execution when any user runs Docker Desktop.\u003cbr\u003e\u003cbr\u003e\u003cstrong\u003eScenario 2 (TOCTOU Attack)\u003c/strong\u003e:\nDuring installation, there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates \u003ccode\u003eC:\\ProgramData\\DockerDesktop\u003c/code\u003e and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files (such as \u003ccode\u003einstall-settings.json\u003c/code\u003e) with attacker-controlled ACLs during this window, achieving the same code execution outcome.\u003cbr\u003e"
}
],
"value": "Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer\u0027s 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."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 6.7,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-732",
"description": "CWE-732 Incorrect Permission Assignment for Critical Resource",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-02-04T13:57:23.002Z",
"orgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e",
"shortName": "Docker"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://docs.docker.com/security/"
},
{
"tags": [
"third-party-advisory"
],
"url": "https://www.zerodayinitiative.com/advisories/ZDI-CAN-28542/"
},
{
"tags": [
"third-party-advisory"
],
"url": "https://www.zerodayinitiative.com/advisories/ZDI-CAN-28190/"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Docker has implemented the following mitigations:\u003cbr\u003e\u003cul\u003e\u003cli\u003eAtomic creation of \u003ccode\u003eC:\\ProgramData\\DockerDesktop\u003c/code\u003e with admin ownership and correct ACLs\u003c/li\u003e\u003cli\u003eVerification that directory is owned by known admin SIDs (SYSTEM or Administrators)\u003c/li\u003e\u003cli\u003eInstallation aborts if directory is not owned by trusted elevated SID\u003c/li\u003e\u003cli\u003eTOCTOU protection through atomic operations setting ownership and ACLs simultaneously\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003eUpdate to Docker Desktop version 4.56 or later.\u003cbr\u003e"
}
],
"value": "Docker has implemented the following mitigations:\n- Atomic creation of C:\\ProgramData\\DockerDesktop with admin ownership and correct ACLs\n- Verification that directory is owned by known admin SIDs (SYSTEM or Administrators)\n- Installation aborts if directory is not owned by trusted elevated SID\n- TOCTOU protection through atomic operations setting ownership and ACLs simultaneously\n\nUpdate to Docker Desktop version 4.56 or later."
}
],
"source": {
"advisory": "ZDI-CAN-28542, ZDI-CAN-28190",
"discovery": "EXTERNAL"
},
"title": "Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e",
"assignerShortName": "Docker",
"cveId": "CVE-2025-14740",
"datePublished": "2026-02-04T13:57:23.002Z",
"dateReserved": "2025-12-15T18:58:24.043Z",
"dateUpdated": "2026-02-05T04:55:14.212Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2025-14740\",\"sourceIdentifier\":\"security@docker.com\",\"published\":\"2026-02-04T14:16:08.533\",\"lastModified\":\"2026-02-04T16:33:44.537\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer\u0027s 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.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@docker.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H\",\"baseScore\":6.7,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"REQUIRED\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":0.8,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"security@docker.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-732\"}]}],\"references\":[{\"url\":\"https://docs.docker.com/security/\",\"source\":\"security@docker.com\"},{\"url\":\"https://www.zerodayinitiative.com/advisories/ZDI-CAN-28190/\",\"source\":\"security@docker.com\"},{\"url\":\"https://www.zerodayinitiative.com/advisories/ZDI-CAN-28542/\",\"source\":\"security@docker.com\"}]}}",
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-14740\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-02-04T16:53:38.263251Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-02-04T16:53:42.734Z\"}}], \"cna\": {\"title\": \"Docker Desktop for Windows Incorrect Permission Assignment Privilege Escalation Vulnerabilities\", \"source\": {\"advisory\": \"ZDI-CAN-28542, ZDI-CAN-28190\", \"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Nitesh Surana (niteshsurana.com) - Trend Micro Zero Day Initiative\"}, {\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Amol Dosanjh - Trend Micro Research\"}], \"impacts\": [{\"capecId\": \"CAPEC-1\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 6.7, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"REQUIRED\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"Docker Inc.\", \"product\": \"Docker Desktop\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"4.56.0\"}], \"platforms\": [\"Windows\"], \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"Docker has implemented the following mitigations:\\n- Atomic creation of C:\\\\ProgramData\\\\DockerDesktop with admin ownership and correct ACLs\\n- Verification that directory is owned by known admin SIDs (SYSTEM or Administrators)\\n- Installation aborts if directory is not owned by trusted elevated SID\\n- TOCTOU protection through atomic operations setting ownership and ACLs simultaneously\\n\\nUpdate to Docker Desktop version 4.56 or later.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Docker has implemented the following mitigations:\u003cbr\u003e\u003cul\u003e\u003cli\u003eAtomic creation of \u003ccode\u003eC:\\\\ProgramData\\\\DockerDesktop\u003c/code\u003e with admin ownership and correct ACLs\u003c/li\u003e\u003cli\u003eVerification that directory is owned by known admin SIDs (SYSTEM or Administrators)\u003c/li\u003e\u003cli\u003eInstallation aborts if directory is not owned by trusted elevated SID\u003c/li\u003e\u003cli\u003eTOCTOU protection through atomic operations setting ownership and ACLs simultaneously\u003c/li\u003e\u003c/ul\u003e\u003cbr\u003eUpdate to Docker Desktop version 4.56 or later.\u003cbr\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"https://docs.docker.com/security/\", \"tags\": [\"vendor-advisory\"]}, {\"url\": \"https://www.zerodayinitiative.com/advisories/ZDI-CAN-28542/\", \"tags\": [\"third-party-advisory\"]}, {\"url\": \"https://www.zerodayinitiative.com/advisories/ZDI-CAN-28190/\", \"tags\": [\"third-party-advisory\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer\u0027s 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.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Docker Desktop for Windows contains multiple incorrect permission assignment vulnerabilities in the installer\u0027s handling of the \u003ccode\u003eC:\\\\ProgramData\\\\DockerDesktop\u003c/code\u003e directory. The installer creates this directory without proper ownership verification, creating two exploitation scenarios:\u003cbr\u003e\u003cbr\u003e\u003cstrong\u003eScenario 1 (Persistent Attack)\u003c/strong\u003e:\\nIf a low-privileged attacker pre-creates \u003ccode\u003eC:\\\\ProgramData\\\\DockerDesktop\u003c/code\u003e 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 \u003ccode\u003einstall-settings.json\u003c/code\u003e to specify a malicious \u003ccode\u003ecredentialHelper\u003c/code\u003e, causing arbitrary code execution when any user runs Docker Desktop.\u003cbr\u003e\u003cbr\u003e\u003cstrong\u003eScenario 2 (TOCTOU Attack)\u003c/strong\u003e:\\nDuring installation, there is a time-of-check-time-of-use (TOCTOU) race condition between when the installer creates \u003ccode\u003eC:\\\\ProgramData\\\\DockerDesktop\u003c/code\u003e and when it sets secure ACLs. A low-privileged attacker actively monitoring for the installation can inject malicious files (such as \u003ccode\u003einstall-settings.json\u003c/code\u003e) with attacker-controlled ACLs during this window, achieving the same code execution outcome.\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-732\", \"description\": \"CWE-732 Incorrect Permission Assignment for Critical Resource\"}]}], \"providerMetadata\": {\"orgId\": \"686469e6-3ff6-451b-ab8b-cf5b9e89401e\", \"shortName\": \"Docker\", \"dateUpdated\": \"2026-02-04T13:57:23.002Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2025-14740\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-02-05T04:55:14.212Z\", \"dateReserved\": \"2025-12-15T18:58:24.043Z\", \"assignerOrgId\": \"686469e6-3ff6-451b-ab8b-cf5b9e89401e\", \"datePublished\": \"2026-02-04T13:57:23.002Z\", \"assignerShortName\": \"Docker\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…