opencontainers · runc · published 2026-07-01
CVE-2026-41579runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-41579 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 8% of all CVEs. This runc vulnerability: CVSS 3.3 (v3.1). Fixed upstream in runc 1.4.3, 1.3.6. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in runc 1.4.3, 1.3.6.
Patch events
Container runtimerunc
runc security releases: 1.4.3, 1.3.6
Upgrade to
1.4.31.3.6Why: Vendor security release for server software (most severe: CVE-2026-41579).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (8th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.3 (v3.1)CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- opencontainers runc
< 1.3.6(affected)>= 1.4.0-rc.1, < 1.4.3(affected)>= 1.5.0-rc.1, < 1.5.0-rc.3(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.