# CVE-2025-10657: Docker Desktop with ECI Fails to Enforce Socket Command Restrictions

> Docker Desktop fails to enforce socket command restrictions when Enhanced Container Isolation is enabled, allowing containers to execute unrestricted Docker commands.

- **Severity:** High 8.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-g3fh-rgmp-4frg

## What is CVE-2025-10657?

CVE-2025-10657 is a high-severity vulnerability in Docker Desktop, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In a hardened Docker environment, with Enhanced Container Isolation ( ECI https://docs.docker.com/enterprise/security/hardened-desktop/enhanced-container-isolation/ ) enabled, an administrator can utilize the command restrictions  feature https://docs.docker.com/enterprise/security/hardened-desktop/enhanced-container-isolation/config/#command-restrictions  to restrict commands that a container with a Docker socket mount may issue on that socket.
Due to a software bug, the configuration to restrict commands was ignored when passed to ECI, allowing any command to be executed on the socket. This grants excessive privileges by permitting unrestricted access to powerful Docker commands.

The vulnerability affects only Docker Desktop 4.46.0 users that have ECI enabled and are using the Docker socket command restrictions feature. In addition, since ECI restricts mounting the Docker socket into containers by default, it only affects containers which are explicitly allowed by the administrator to mount the Docker socket.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-10657?


## How do I fix CVE-2025-10657?

No fix has been published for CVE-2025-10657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10657 being exploited?

There is no known exploitation of CVE-2025-10657 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10657 and fix it if it is affected.

What it is: CVE-2025-10657 is a high-severity vulnerability in Docker Desktop, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10657 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10657/ (Markdown: https://insights.sbomify.com/CVE-2025-10657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10657
- OSV: https://osv.dev/vulnerability/CVE-2025-10657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10657/
Summaries are generated and may contain mistakes; the official description above is the record.