CVE-2025-9074

{"id": "CVE-2025-9074", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.3, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-08-20T14:15:49.047", "references": [{"url": "https://docs.docker.com/desktop/release-notes/#4443", "source": "[email protected]"}, {"url": "https://blog.qwertysecurity.com/Articles/blog3.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://pvotal.tech/breaking-dockers-isolation-using-docker-cve-2025-9074/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.bleepingcomputer.com/news/security/critical-docker-desktop-flaw-lets-attackers-hijack-windows-hosts/", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.vicarius.io/vsociety/posts/cve-2025-9074-detect-docker-desktop-vulnerability", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://www.vicarius.io/vsociety/posts/cve-2025-9074-mitigate-docker-desktop-vulnerability", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://blog.qwertysecurity.com/Articles/blog3", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}, {"url": "https://pvotal.tech/breaking-dockers-isolation-using-docker-cve-2025-9074/", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-668"}]}], "descriptions": [{"lang": "en", "value": "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.\nThis 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."}, {"lang": "es", "value": "Se identific\u00f3 una vulnerabilidad en Docker Desktop que permite a los contenedores Linux locales acceder a la API del motor Docker a trav\u00e9s de la subred de Docker configurada, 192.168.65.7:2375 por defecto. Esta vulnerabilidad se produce con o sin el Aislamiento Mejorado de Contenedores (ECI) habilitado, y con o sin la opci\u00f3n \"Exponer daemon en tcp://localhost:2375 sin TLS\". Esto puede provocar la ejecuci\u00f3n de una amplia gama de comandos privilegiados en la API del motor, incluyendo el control de otros contenedores, la creaci\u00f3n de nuevos, la gesti\u00f3n de im\u00e1genes, etc. En algunas circunstancias (por ejemplo, Docker Desktop para Windows con backend WSL), tambi\u00e9n permite montar la unidad host con los mismos privilegios que el usuario que ejecuta Docker Desktop."}], "lastModified": "2025-09-25T17:15:39.650", "sourceIdentifier": "[email protected]"}