Skip to content
vulneraibility.com
Screener

CVE-2025-9074

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.

CVSS
Not scored yetNVD has not published a score
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
1.9%chance of exploitation in the next 30 daystop 20% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
20 Aug 2025analysed here 12 Nov 2026

NVD hasn't published a CVSS score for this CVE yet. Severity and the CVSS vector appear here once it is scored upstream.

Summary

Triage

Exploitable
At runtime
Attack vector
local
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Docker Docker Desktop>= 4.25 and < 4.44.3Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 on Exploit-DB · 18 GitHub proofs of concept
CISA SSVC
exploitation poc, automatable no, technical impact totalAssessed by CISA 26 Aug 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Exploit-DB

GitHub proofs of concept

and 14 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 20 Aug 2025Published
  2. 23 Aug 2025First public exploit or proof of concept2 days later
  3. 26 Aug 2025CISA SSVC assessment: exploitation poc3 days later
  4. 26 Feb 2026CVE record last updated185 days (about 6 months) later
  5. 12 Nov 2026Analysed by vulneraibility.com259 days (about 9 months) later

Common questions

Is CVE-2025-9074 being exploited?

Not confirmed. CVE-2025-9074 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.9% probability of exploitation in the next 30 days.

How severe is CVE-2025-9074?

No severity score has been published for CVE-2025-9074 yet. Since April 2026 the NVD enriches only prioritised CVEs, so an unscored record means nobody has assessed it — not that the flaw is minor. Judge it from the vendor advisory and whether you run the affected software.

Is there a patch for CVE-2025-9074?

Yes. A fix has been recorded for CVE-2025-9074. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

7 references in the CVE record, grouped by the tags the record gives them.

Exploits (2)

Other links (5)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com