CVE-2024-21626: Leaky Vessels: runc File-Descriptor Leak Container Escape
- Vendors
- Fedora ProjectLinux Foundation
CVE-2024-21626 is a container-escape vulnerability in runc 1.1.11 and earlier caused by leaked internal file descriptors and insufficient working-directory validation. A specially configured container process launched through runc run or runc exec can retain a working directory in the host filesystem namespace, providing access outside the container filesystem. Malicious container images can trigger the runc run attack path, while an attacker controlling an existing container can prepare conditions for exploitation during a subsequent runc exec operation. Additional variants permit overwriting semi-arbitrary host binaries and can lead to complete container escape. The vulnerability also affects higher-level container platforms that use vulnerable runc versions. Upstream runc 1.1.12 fixes the issue.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation breaches container filesystem isolation, exposing host data and potentially allowing modification of host files. Host-binary overwrite variants can lead to host code execution and complete container escape. A compromised container host or Kubernetes node can expose credentials, other workloads, and shared infrastructure, enabling lateral movement and service disruption. In Docker Desktop on macOS, the immediate escape target is the LinuxKit virtual machine rather than the macOS host directly.
Mitigation
If you can’t patch tonight, do this now.
Until patched, run only trusted images, restrict container process.cwd settings to the container root directory, and avoid runc exec operations, including those invoked indirectly by higher-level runtimes. Working-directory restrictions do not address every variant: attack 3b has no practical workaround other than avoiding runc exec. Review untrusted images, Dockerfiles, and workload configurations for attempted exploitation. These controls are temporary exposure reductions, not substitutes for updating runc.
Remediation
Patch, then assume compromise.
Upgrade upstream runc to 1.1.12 or later, or install a distribution-supported package containing the backported fix; an older upstream version number alone does not establish that a vendor package remains vulnerable. The patches validate that the working directory is inside the container, close internal file descriptors before execution, fix descriptor leaks, and enforce close-on-exec handling. Update bundled container-platform components through vendor-supported releases; identified fixed releases include Docker Engine/Moby 25.0.2, Docker Desktop 4.27.1, and Talos Linux 1.5.6 or 1.6.4 in their respective release lines. Replace or restart managed-service resources where required to activate the patched runtime.
Exploits
9 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2024-21626 exploited in the wild?
- Yes. As of Nov 15, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2024-21626?
- Yes. Mallory tracks 9 public exploits or proofs of concept for CVE-2024-21626, the earliest disclosed Jan 31, 2024.
- Is there a patch for CVE-2024-21626?
- Upgrade upstream runc to 1.1.12 or later, or install a distribution-supported package containing the backported fix; an older upstream version number alone does not establish that a vendor package remains vulnerable. The patches validate that the working directory is inside the container, close internal file descriptors before execution, fix descriptor leaks, and enforce close-on-exec handling.
- What products are affected by CVE-2024-21626?
- Linux Foundation Runc and Fedora Project Fedora.
- How severe is CVE-2024-21626?
- CVE-2024-21626 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 18.9% (97th percentile) as of Nov 15, 2026.
Recent activity
40 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.