CVE-2025-10657
BaseFortify
Publication date: 2025-09-26
Last updated on: 2025-09-29
Assigner: Docker Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| docker | docker_desktop | 4.46.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Docker Desktop 4.46.0 when Enhanced Container Isolation (ECI) is enabled along with the Docker socket command restrictions feature. Due to a software bug, the command restrictions intended to limit what commands a container with a Docker socket mount can execute are ignored. This allows any command to be executed on the Docker socket, granting excessive privileges and unrestricted access to powerful Docker commands.
How can this vulnerability impact me? :
If you are using Docker Desktop 4.46.0 with ECI enabled and have containers explicitly allowed to mount the Docker socket, this vulnerability can allow those containers to execute any Docker command without restriction. This could lead to privilege escalation, unauthorized control over Docker operations, and potentially compromise the host system or other containers.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that you are not using Docker Desktop version 4.46.0 with Enhanced Container Isolation (ECI) enabled and the Docker socket command restrictions feature active. Since the vulnerability only affects containers explicitly allowed to mount the Docker socket, review and restrict any containers that have the Docker socket mounted. Consider disabling the command restrictions feature until a patch is available or upgrading Docker Desktop to a version where this bug is fixed.