cve.bz

CVE-2025-9074 docker docker desktop: Exposure of Resource to Wrong Sphere

9.3 criticalExploitEPSS 2.0%

Critical (9.3) in docker docker desktop. EPSS 2.0% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
2.0% (unchanged from 1.9% a week ago; 1.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 81st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-08-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-9074 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-9074?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-9074?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-9074 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Docker Desktopfrom 4.25 before 4.44.3

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • BridgerAlderson/CVE-2025-9074-PoC Harbor Check: matches CVE 49 stars, Shell, created
    A vulnerability has been identified in Docker Desktop. A remote attacker could exploit this vulnerability to trigger security restriction b…
  • Shaoshi17/CVE-2025-9074-Docker-Exploit Harbor Check: matches CVE 13 stars, Python, created
    一个功能强大的 Docker 远程 API 漏洞利用工具,用于 CVE-2025-9074 漏洞的安全研究和测试。
  • zenzue/CVE-2025-9074 Harbor Check: matches CVE 11 stars, created
  • j3r1ch0123/CVE-2025-9074 Harbor Check: matches CVE 8 stars, created
    New vulnerability found in Docker. Credit for finding the vulnerability goes to Felix Boulet
  • OilSeller2001/PoC-for-CVE-2025-9074 Harbor Check: matches CVE 5 stars, created
    Proof-of-Concept exploit for CVE-2025-9074 - Unauthenticated Docker API exposure allowing arbitrary container creation and host filesystem …
13 more

References

Check your stackJSON