cve.bz

CVE-2026-41579 linuxfoundation runc: UNIX Symbolic Link (Symlink) Following

3.3 lowEPSS 0.2%Fix available

Low (3.3) in linuxfoundation runc. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/opencontainers/runc 1.3.6, 1.4.3, 1.5.0-rc.3.

On this page
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.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41579 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41579?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41579?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41579 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:runcbefore 1.3.6
linuxfoundation:runcfrom 1.4.0 before 1.4.3
linuxfoundation:runc1.5.0:rc1
linuxfoundation:runc1.5.0:rc2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xjvp-4fhw-gc47Gogithub.com/opencontainers/runc<1.3.61.3.6
GHSA-xjvp-4fhw-gc47Gogithub.com/opencontainers/runc>=1.4.0 <1.4.31.4.3
GHSA-xjvp-4fhw-gc47Gogithub.com/opencontainers/runc>=1.5.0-rc.1 <1.5.0-rc.31.5.0-rc.3
GO-2026-5761Gogithub.com/opencontainers/runc<1.3.6
>=1.4.0 <1.4.3
>=1.5.0-rc.1 <1.5.0-rc.3
1.3.6, 1.4.3, 1.5.0-rc.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13runcno fix listedDEBIAN-CVE-2026-41579
Debian14runc1.3.6+ds1-1DEBIAN-CVE-2026-41579
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTSrunc, runc-appno fix listedUBUNTU-CVE-2026-41579
Ubuntu25.10, 26.04:LTS, 26.10runc, runc-app, runc-stableno fix listedUBUNTU-CVE-2026-41579
UbuntuPro:16.04:LTS, Pro:18.04:LTSruncno fix listedUBUNTU-CVE-2026-41579
SUSEEnterprise Storage 7.1, Linux Enterprise Micro 5.3, Linux Enterprise Micro 5.4 and 2 morerunc1.3.6-150000.101.1SUSE-SU-2026:3433-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 7 morerunc1.3.6-150000.101.1SUSE-SU-2026:3433-2
SUSELinux Enterprise Server 12 SP5-LTSSrunc1.3.6-16.76.1SUSE-SU-2026:3428-2
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0runc1.3.6-160000.1.1SUSE-SU-2026:22942-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5runc1.3.6-16.76.1SUSE-SU-2026:3428-1
SUSELinux Micro 6.0runc1.3.6-1.1SUSE-SU-2026:23047-1
SUSELinux Micro 6.1runc1.3.6-slfo.1.1_1.1SUSE-SU-2026:23164-1
SUSELinux Micro 6.2runc1.3.6-160000.1.1SUSE-SU-2026:22938-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSELeap 16.0runc1.3.6-160000.1.1openSUSE-SU-2026:21431-1
openSUSETumbleweedrunc1.4.3-1.1openSUSE-SU-2026:11301-1
Alpinev3.23, v3.24runc1.4.3-r0ALPINE-CVE-2026-41579
Azure Linux3runc1.3.6-1AZL-91590
Alpaquita23, 25runc1.3.6-r0BELL-CVE-2026-41579
Alpaquitastreamrunc1.4.3-r0BELL-CVE-2026-41579

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

On Red Hat Enterprise Linux and Red Hat CoreOS, this issue is reachable through higher-level runtimes that use runc without Docker’s read-only layer masking (for example Podman on RHEL and CRI-O on RHCOS). Red Hat scores this as a Low impact integrity issue: a malicious image that is run can cause only limited host filesystem changes (deletion of files named ptmx, or creation of a fixed set of symlinks). SELinux in enforcing mode and user-namespace/rootless configurations may further reduce practical impact but are not treated as a complete fix.

Red Hat's mitigation

Run only trusted images.Prefer rootless or user-namespace configurations where practical, and keep SELinux in enforcing mode so host filesystem impact is further limited. These steps reduce exposure but do not fully eliminate the flaw; upgrade to a fixed runc release as soon as it is available.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8container-tools:rhel8/runcFix deferred
Red Hat Enterprise Linux 9runcFix deferred
Red Hat Hardened ImagesbuildahNot affected
Red Hat Hardened ImagespodmanNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Under investigation
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 4runcFix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5runcFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-41579.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON