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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/opencontainers/runc/commit/864db8042dbb Patch
- https://github.com/opencontainers/runc/security/advisories/GHSA-xjvp-4fhw-gc47 Mitigation, Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 3.3 · linuxfoundationNVD modified 2026-10-25 17:10
Affected (CPE criteria) 3
cpe:2.3:a:linuxfoundation:runc:*:*:*:*:*:*:*:*cpe:2.3:a:linuxfoundation:runc:1.5.0:rc1:*:*:*:*:*:*cpe:2.3:a:linuxfoundation:runc:1.5.0:rc2:*:*:*:*:*:*
References 2
- https://github.com/opencontainers/runc/commit/864db8042dbb Patch
- https://github.com/opencontainers/runc/security/advisories/GHSA-xjvp-4fhw-gc47 Mitigation, Patch, Vendor Advisory