CVE-2025-9074
A vulnerability was identified in Docker Desktop that allows local …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- docs.docker.com/desktop/release-notes/#4443
- blog.qwertysecurity.com/Articles/blog3.html
- pvotal.tech/breaking-dockers-isolation-using-docker-cve-2025-9074/
- www.bleepingcomputer.com/news/security/critical-docker-desktop-flaw-lets-attackers-hijack-
- www.vicarius.io/vsociety/posts/cve-2025-9074-detect-docker-desktop-vulnerability
- www.vicarius.io/vsociety/posts/cve-2025-9074-mitigate-docker-desktop-vulnerability
- blog.qwertysecurity.com/Articles/blog3
- nvd.nist.gov/vuln/detail/CVE-2025-9074
- cve.org/CVERecord?id=CVE-2025-9074
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.