Servers and applications
CVE-2026-41579
malicious image with /dev symlink can trigger limited host filesystem integrity violations
- Severity
- Low 3.3
- Published
- 13 Jun 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 1.3.6, 1.4.3
- Exploit chance
- 0.2% in the next 30 daysHigher than 8% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-61
- Attack
- Needs local access · No login needed · Needs someone to click or open something
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Also known as
- GHSA-xjvp-4fhw-gc47
- Sources
- NVD, Project advisories (GitHub)
Description
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.
Please note that this issue is not exploitable under Docker because it creates a top-level ro layer that masks any malicious /dev symlink present in the container image (this is also done without mounting the lower layers so there is no opportunity for the malicious /dev symlink to trick it into resolving to some other path). Unfortunately, Podman and containerd† do not do this and so users using those higher-level runtimes with runc can be exploited via a malicious image.
This issue mirrors a somewhat similar issue in crun, which was also published recently.
Workarounds
Using user namespaces restricts this attack fairly significantly such that the attacker can only create/delete inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actual user on the host (such as with rootless containers that don't use /etc/sub[ug]id), this in practice means that an attacker would only be able to create or delete inodes in world-writable directories.
LSMs can restrict the scope of where in the host filesystem runc can be tricked into operating on, though how much this helps is questionable.
Affected software
| Software | Affected versions |
|---|---|
runcServers and applications · cpe:a:linuxfoundation:runc |
|
runcServers and applications · github:opencontainers/runc |
|
About runc
CLI tool for spawning and running containers according to the OCI specification
- GitHub stars
- 13,557GitHub, 15 Nov 2026
- Forks
- 2,352GitHub, 15 Nov 2026
- Latest release
- v1.5.3GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 5 Jun 2015GitHub
Vulnerabilities in runc
- In our list
- 19
- Published in the last 12 months
- 2
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-119101malicious image can bind-mount an arbitrary host directory into a container across checkpoint/restoreHigh 7.9 12 Nov 2026
- CVE-2025-52565container escape with malicious config due to /dev/console mount and related racesHigh 8.4 5 Nov 2025
- CVE-2025-52881container escape and denial of service due to arbitrary write gadgets and procfs write redirectsHigh 7.3 5 Nov 2025
- CVE-2025-31133container escape via "masked path" abuse due to mount race conditionsHigh 7.3 5 Nov 2025
- CVE-2024-45310runc can be tricked into creating empty files/directories on the hostLow 3.6 3 Sept 2024
- CVE-2024-21626several container breakouts due to internally leaked fdsHigh 8.6 31 Jan 2024
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-41579
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41579
- GitHub Advisory Database https://github.com/advisories/GHSA-xjvp-4fhw-gc47
- github.com https://github.com/opencontainers/runc/security/advisories/GHSA-xjvp-4fhw-gc47