CVE-2026-41579

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

LOW
3.3
CVSS Score
Published: July 1, 2026 at 12:02 AM UTC
Updated: October 25, 2026 at 05:10 PM UTC
2 products affected across 2 vendorsRuncRunc

Using runc by opencontainers?

Get instant alerts when new vulnerabilities affect runc - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.3.61.4.0 ≤ v < 1.4.31.5.01.5.0 rc11.5.0 rc2
Affected range stops below 1.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.4.3, so it looks safe — our inference, not a vendor statement
v < 1.3.6
Affected range stops below 1.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.4.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.5.0-rc.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMMitigationPatchVendor Advisory
Source: cverecord
https://github.com/opencontainers/runc/security/advisories/GHSA-xjvp-4fhw-gc47

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.3LOWGitHub_M
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-61

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card