Loading story…
A high-severity path traversal vulnerability, tracked as CVE-2025-62725, was discovered in Docker Compose's handling of OCI-based Compose artifacts. The flaw allowed attackers to exploit the way Docker Compose processed layer annotations such as com.docker.compose.file and com.docker.compose.envfile, enabling them to escape the intended cache directory and write arbitrary files to the host system. This vulnerability could be triggered by tricking a user into referencing a malicious remote artifact, and affected a wide range of environments including Docker Desktop, standalone Compose binaries on Linux, CI/CD runners, and cloud development environments.
The vulnerability was rated High with a CVSS score of 8.9 and could be exploited even through read-only commands like docker compose config or docker compose ps. The issue was patched in Docker Compose version v2.40.2, and users are strongly advised to upgrade to this version or later to mitigate the risk. The vulnerability was responsibly disclosed and detailed technical analysis, including proof of concept and exploitation scenarios, has been published to aid defenders in understanding and addressing the issue.
See real exploitation activity before you spend the cycle.
3 events from the most recent confirmed update back to the earliest known activity.
By 2025-10-28, public technical analysis described how CVE-2025-62725 could be triggered through commands such as `docker compose ps` or `docker compose config`, not only when starting containers. A proof of concept demonstrated overwriting `~/.ssh/authorized_keys` to gain SSH access after a victim referenced a crafted remote artifact.
On 2025-10-27, Docker issued a security advisory for CVE-2025-62725 affecting Docker Compose versions prior to v2.40.2. The advisory warned that OCI artifact layer annotations could be abused for arbitrary file overwrite and urged users to upgrade.
On 2025-10-27, Docker confirmed CVE-2025-62725, a high-severity path traversal flaw in Docker Compose's OCI artifact handling, and released Docker Compose v2.40.2 to address it. The fix added path validation to prevent writes outside the cache directory.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
4 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcecyber.gc.ca
Open sourceimperva.com
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Docker disclosed a high-severity Docker Engine vulnerability, **CVE-2026-34040** (`CVSS 8.8`), that allows attackers to bypass authorization plugins and perform actions that should be blocked. The flaw stems from an incomplete fix for **CVE-2024-41110** and is triggered when a specially crafted oversized Docker API request causes the request body to be dropped before inspection by an AuthZ plugin. In affected environments, the plugin may approve container operations it would otherwise deny, opening a path to unauthorized privileged actions and potential host compromise. Researchers said an attacker with Docker API access could exploit the bug by padding a container-creation request beyond **1 MB** to launch a privileged container with access to the host filesystem, exposing sensitive assets such as **AWS credentials**, **SSH keys**, and **Kubernetes configurations**. The issue affects deployments that rely on authorization plugins inspecting request bodies, while environments not using those plugins are not impacted. Docker patched the vulnerability in **Docker Engine 29.3.1** and urged defenders to upgrade, restrict Docker API access, avoid AuthZ plugins that depend on request-body inspection, and use controls such as rootless mode, user namespace remapping, and least-privilege access to reduce risk.
Jul 23, 2026
A critical path traversal flaw tracked as **`CVE-2026-56260`** allows unauthenticated remote attackers to write arbitrary files on servers running vulnerable versions of **Crawl4AI**. The issue affects the Docker API server’s **`/screenshot`** and **`/pdf`** endpoints, where the **`output_path`** parameter accepts absolute paths and directory traversal sequences without proper validation. The vulnerability impacts versions up to and including **`0.8.6`** and was fixed in **`0.8.7`**. By overwriting files writable by the application user, attackers could cause denial of service and compromise system integrity, including planting SSH authorized keys or injecting cron jobs for persistence. The flaw is classified as **`CWE-22`** and carries a **CVSS 9.1** rating with network-based, unauthenticated exploitation potential. Reports said no public proof-of-concept or confirmed active exploitation had emerged at publication time, and advised organizations to upgrade immediately or restrict access to the exposed endpoints as a compensating control.
Jul 13, 2026
Security researchers have disclosed three critical vulnerabilities in the runC container runtime, which is widely used in platforms such as Docker and Kubernetes. The flaws, identified as CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881, arise from logic and race-condition errors in runC's handling of temporary bind mounts, symbolic links, and certain write operations. Attackers can exploit these weaknesses to break container isolation, potentially gaining write access to sensitive host system files and kernel interfaces such as `/proc/sys/kernel/core_pattern` or `/proc/sysrq-trigger`, leading to full container escapes and even host-level compromise. The vulnerabilities allow attackers to abuse masked paths, console bind-mounts, and redirected writes, bypassing standard hardening and isolation controls. Exploitation requires either custom mount configurations or the use of untrusted container images, but the risk is significant for orchestrated environments like Docker and Kubernetes. Security advisories from both the runC project and the U.S. National Vulnerability Database urge immediate updates to patched versions or the application of provided patches to mitigate these threats. The vulnerabilities highlight the importance of robust container runtime security and the potential impact of logic flaws in core infrastructure components.
Jun 29, 2026