Docker Compose anfällig für Pfadübersprung über OCI Artifact Layer Annotations in github.com/docker/compose

The core of the vulnerability lies in how Docker Compose processes annotations within OCI (Open Container Initiative) artifact layers. Malicious actors can craft specially designed annotations that, when processed by Docker Compose, lead to the traversal of directories outside the intended scope. This allows them to read files they shouldn't have access to, potentially exposing configuration files, secrets, or other sensitive data. The impact can range from information disclosure to, in more complex scenarios, potential code execution if the attacker can leverage the read access to manipulate system behavior. While direct code execution isn't immediately apparent, the ability to read arbitrary files creates a significant attack surface.

Organizations using Docker Compose in production environments, particularly those with sensitive data stored on the host system or within Docker containers, are at risk. Environments with less stringent file access controls are also more vulnerable. Developers using Docker Compose for local development should also apply the fix to prevent potential compromise.

• linux / server: Monitor Docker Compose logs for unusual file access attempts. Use journalctl -u docker-compose to filter for errors related to file access.

journalctl -u docker-compose | grep "file not found" -i

• go: Inspect Docker Compose source code for instances of os.Open or similar functions that handle file paths derived from user input. Look for potential path traversal vulnerabilities. • generic web: If Docker Compose is exposed via a web interface, monitor access logs for requests attempting to access files outside the intended directory.

1. 2025-10-30Disclosure

   disclosure

1. Reserviert2025-10-20
2. Veröffentlicht2025-10-30
3. Geändert2026-03-03
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2025-62725 is to upgrade Docker Compose to version 2.40.2 or later. This version includes a fix that properly sanitizes and validates OCI artifact layer annotations, preventing the path traversal. If an immediate upgrade is not feasible, consider implementing stricter file system permissions to limit the potential damage from a successful exploit. While a WAF or proxy cannot directly prevent this vulnerability, they can be configured to monitor for suspicious file access patterns. After upgrading, verify the fix by attempting to access a file outside the expected directory using a crafted OCI annotation; the access should be denied.