Docker Desktop: Container-to-host write via exposed Engine API (CVE-2025-9074)
A public proof-of-concept for CVE-2025-9074 demonstrates that the Docker Engine API exposure on Docker Desktop for Windows allows container escape and unauthorized host file system access.
CVE search metadata
CVE search record: CVE-2025-9074. EPSS: 1.83%. KEV: no. Product: Docker Desktop. Brief: Docker Desktop: Container-to-host write via exposed Engine API (CVE-2025-9074). Brief link: https://feed.craftedsignal.io/briefs/2026-10-docker-desktop-cve-2025-9074/
Triage facts
Revision 1- Applicability
- Docker Desktop
- Evidence
- Unknown
- Severity
- High
- Action
- Immediate escalation
- Sources
- 2 public sources
- Freshness
- Revision 1Oct 23, 19:48 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- B2Likely
CVE-2025-9074 is a vulnerability in Docker Desktop for Windows where the Docker Engine HTTP API is reachable from within containers at 192.168.65.7:2375 without authentication. An attacker with container-level access can interact with this API to create new containers with bind mounts to the host Windows file system, enabling full read/write access to the host machine.
Attack Chain
- Attacker gains initial access to a container running on the target Docker Desktop instance.
- Attacker performs discovery to identify the reachable Docker Engine API endpoint (192.168.65.7:2375).
- Attacker validates reachability by sending a GET request to the /_ping endpoint.
- Attacker constructs a malicious API request to the /containers/create endpoint.
- Attacker specifies a HostConfig bind mount in the request body, mapping the host's Windows C drive to a directory inside the new container.
- Attacker spawns the container and executes commands to write or modify files on the underlying Windows host.
Impact
Successful exploitation allows for container escape, arbitrary file write, and host-level interaction, potentially leading to full system compromise of the Windows host.
Recommendation
- Update Docker Desktop for Windows to the latest patched version.
- Audit and restrict access to the Docker Engine API; ensure it is not exposed over HTTP to containers or untrusted networks.
- Implement network policies to block container-to-container or container-to-host traffic to the Docker API port (2375).
- Implement monitoring for unauthorized container creation events originating from within existing containers.
Immediate actions
Check Docker Desktop version and apply patches
Threat Hunt
Identify container processes performing unauthorized file operations on the host C: drive.
Data: File integrity monitoring logs, Docker daemon audit logs
Mitigations
Ensure the Docker Engine API is not exposed over plain HTTP
CVE-2025-9074