runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem ("attack 2"). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run ("attack 1"). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes ("attack 3a" and "attack 3b"). runc 1.1.12 includes patches for this issue.
[POC] CVE-2024-21626 — CVE-2024-21626
CVE-2024-21626-poc-research-Reappearance-andtodo
[POC] CVE-2024-21626 — CVE-2024-21626
PoC and Detection for CVE-2024-21626
[POC] CVE-2024-21626 — CVE-2024-21626-PoC
Root cuase & Proof of cause
[POC] CVE-2024-21626 — little-joke
Some scripts to simulate an attack (used for CVE-2024-21626)
[POC] CVE-2024-21626 — cve-2024-21626-runc-1.1.11-escape
PoC for CVE-2024-21626: runc leaks an internal fd referencing the host CWD before pivot_root, enabling container escape by setting process.cwd to /proc/self/fd/7
[POC] CVE-2024-21626 — CVE-2024-21626-demo
Container Runtime Meetup #5 のLT用のデモ
[POC] CVE-2024-21626 — CVE-2024-21626
POC
[POC] CVE-2024-21626 — container-escape-ebpf
POCs and Tetragon Rules for CVE-2024-21626 and CVE-2025-31133
X (Twitter) Discussion
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Get alerted for CVEs like this
Register your stack and get notified within minutes when a matching CVE drops.
Start monitoring free