Directory Traversal Affecting docker-compose package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN12-DOCKERCOMPOSE-13733863
- published29 Oct 2025
- disclosed27 Oct 2025
Introduced: 27 Oct 2025
NewCVE-2025-62725 (opens in a new tab)How to fix?
There is no fixed version for Debian:12 docker-compose.
NVD Description
Note: Versions mentioned in the description apply only to the upstream docker-compose package and not the docker-compose package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Docker Compose trusts the path information embedded in remote OCI compose artifacts. When a layer includes the annotations com.docker.compose.extends or com.docker.compose.envfile, Compose joins the attacker‑supplied value from com.docker.compose.file/com.docker.compose.envfile with its local cache directory and writes the file there. This affects any platform or workflow that resolves remote OCI compose artifacts, Docker Desktop, standalone Compose binaries on Linux, CI/CD runners, cloud dev environments is affected. An attacker can escape the cache directory and overwrite arbitrary files on the machine running docker compose, even if the user only runs read‑only commands such as docker compose config or docker compose ps. This issue is fixed in v2.40.2.