What is CVE-2025-62725?

CVE-2025-62725 is a high-severity improper input validation vulnerability in github.com/docker/compose/v2 (go), affecting versions >= 2.34.0, < 2.40.2. It is fixed in 2.40.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which versions of github.com/docker/compose/v2 are affected by CVE-2025-62725?

github.com/docker/compose/v2 (go) versions >= 2.34.0, < 2.40.2 is affected.

Is there a fix for CVE-2025-62725?

Yes. CVE-2025-62725 is fixed in 2.40.2. Upgrade to this version or later.

Is CVE-2025-62725 exploitable, and should I be worried?

Whether CVE-2025-62725 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-62725 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-62725?

Upgrade github.com/docker/compose/v2 to 2.40.2 or later.

CVE-2025-62725 in github.com/docker/compose/v2

Q: Which versions of github.com/docker/compose/v2 are affected by CVE-2025-62725?

github.com/docker/compose/v2 (go) versions >= 2.34.0, < 2.40.2 is affected.

Q: Is there a fix for CVE-2025-62725?

Yes. CVE-2025-62725 is fixed in 2.40.2. Upgrade to this version or later.

Q: Is CVE-2025-62725 exploitable, and should I be worried?

Whether CVE-2025-62725 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-62725 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-62725?

Upgrade github.com/docker/compose/v2 to 2.40.2 or later.

Summary

Docker Compose Vulnerable to Path Traversal via OCI Artifact Layer Annotations

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.

Workarounds

Impact

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

github.com/docker/compose/v2 (>= 2.34.0, < 2.40.2)

Security releases

github.com/docker/compose/v2 → 2.40.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

v2.40.2

Frequently Asked Questions

What is CVE-2025-62725? CVE-2025-62725 is a high-severity improper input validation vulnerability in github.com/docker/compose/v2 (go), affecting versions >= 2.34.0, < 2.40.2. It is fixed in 2.40.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which versions of github.com/docker/compose/v2 are affected by CVE-2025-62725? github.com/docker/compose/v2 (go) versions >= 2.34.0, < 2.40.2 is affected.
Is there a fix for CVE-2025-62725? Yes. CVE-2025-62725 is fixed in 2.40.2. Upgrade to this version or later.
Is CVE-2025-62725 exploitable, and should I be worried? Whether CVE-2025-62725 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-62725 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-62725? Upgrade github.com/docker/compose/v2 to 2.40.2 or later.