CVE-2025-9074: Docker Desktop allows unauthenticated access to Docker Engine API from containers
A vulnerability was identified in Docker Desktop that allows local running Linux containers to access the Docker Engine API via the configured Docker subnet, at 192.168.65.7:2375 by default. This vulnerability occurs with or without Enhanced Container Isolation (ECI) enabled, and with or without the "Expose daemon on tcp://localhost:2375 without TLS" option enabled. This can lead to execution of a wide range of privileged commands to the engine API, including controlling other containers, creating new ones, managing images etc. In some circumstances (e.g. Docker Desktop for Windows with WSL backend) it also allows mounting the host drive with the same privileges as the user running Docker Desktop.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-9074?
CVE-2025-9074 is considered a high severity vulnerability due to its potential to expose the Docker Engine API to unauthorized access.
How do I fix CVE-2025-9074?
To mitigate CVE-2025-9074, restrict access to the Docker Engine API by modifying your firewall rules or upgrading to the latest version of Docker Desktop that addresses this issue.
Which versions of Docker Desktop are affected by CVE-2025-9074?
CVE-2025-9074 affects multiple versions of Docker Desktop prior to the fix included in version 4.4.3.
Can CVE-2025-9074 be exploited without Enhanced Container Isolation?
Yes, CVE-2025-9074 can be exploited regardless of whether Enhanced Container Isolation is enabled or disabled.
What components of Docker are involved in CVE-2025-9074?
CVE-2025-9074 involves the Docker Engine API and the local network configuration allowing access through the predefined Docker subnet.