CVE-2026-41579 runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

Low 3.3 Published Updated

A malicious container image can trick runc into deleting host files or creating symlinks, compromising host filesystem integrity.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-41579?

CVE-2026-41579 is a low-severity path traversal vulnerability in opencontainers runc, published on 1 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official 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.

Weakness: CWE-61

Which versions are affected by CVE-2026-41579?

7 open source packages ship an affected version, including github.com/opencontainers/runc. It affects 1 product.

PackageAffectedFixed in
github.com/opencontainers/runc GoAll versions1.3.6, 1.4.3, 1.5.0-rc.3
github.com/opencontainers/runc GoAll versions1.3.6
github.com/opencontainers/runc GoAll versions1.3.6
github.com/opencontainers/runc GoFrom 1.4.01.4.3
github.com/opencontainers/runc GoFrom 1.4.01.4.3
github.com/opencontainers/runc GoFrom 1.5.0-rc.11.5.0-rc.3
1 more packages
github.com/opencontainers/runc GoFrom 1.5.0-rc.11.5.0-rc.3
Linux distribution packages (14)
runc SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server 12 SP5-LTSSAll versions1.3.6-16.76.1
runc SUSE:Linux Enterprise Server 15 SP4-LTSSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server 15 SP5-LTSSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server 15 SP6-LTSSAll versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server for SAP Applications 15 SP4All versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server for SAP Applications 15 SP5All versions1.3.6-150000.101.1
runc SUSE:Linux Enterprise Server for SAP Applications 15 SP6All versions1.3.6-150000.101.1
runc SUSE:Linux Micro 6.0All versions1.3.6-1.1
runc SUSE:Linux Micro 6.1All versions1.3.6-slfo.1.1_1.1
runc openSUSE:TumbleweedAll versions1.4.3-1.1

Products include Linuxfoundation Runc.

How do I fix CVE-2026-41579?

Upgrade github.com/opencontainers/runc to a fixed version for your release line: 1.3.6, 1.4.3 or 1.5.0-rc.3.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-41579 being exploited?

There is no known exploitation of CVE-2026-41579 in the wild and no public exploit code.

Sources

Also known as AZL-91590, BELL-CVE-2026-41579, CLEANSTART-2026-GY71678, CLEANSTART-2026-RD37922, CLSA-2026-1783518302, CLSA-2026-1784034091 and 42 more.

Is CVE-2026-41579 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free