CVE-2026-41579
runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations
runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.
- Affected
- opencontainers · runc
- CVSS v4.0 GitHub
- 4.8 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N - CVSS v3.1 GITHUB
- 3.3 LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N - EPSS
- 0.19% chance of exploitation in the next 30 days, 8th percentile
- Published
- 2026-07-01
Proof-of-concept exploits (1)
- Prathmesh234/runc-poc0★ · 2026-09-04
Security advisories
- opencontainers/runc/security/advisories/GHSA-xjvp-4fhw-gc47
- advisories/GHSA-xjvp-4fhw-gc47
- opencontainers/runc/commit/864db8042dbb