Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41579: runc is a CLI tool for spawning and running containers according to the OCI specification

19
Routine
LOW 3.3WATCHLISTUPGRADE

CVE-2026-41579 is a low-severity flaw (CVSS 3.3) affecting runc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 spec

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score3.3 (Low)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.2% (top 92%)
CISA exploited listNo
WeaknessCWE-61
Published2026-07-01
Last modified2026-10-25
Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

linuxfoundation runc UPGRADE
Affected: < 1.3.6 · >= 1.4.0 and < 1.4.3 · 1.5.0 rc1 · 1.5.0 rc2
Fixed in: 1.3.6, 1.4.3
Safe to downgrade to: a release before 1.4.0
1. Check installed version
apt-cache policy runc || rpm -q runc || runc --version
2. UPGRADE to 1.3.6 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade runc
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade runc
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.4.0 (Debian / Ubuntu)
apt-cache madison runc sudo apt install runc=<VERSION_BEFORE_1.4.0> sudo apt-mark hold runc
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list runc sudo dnf downgrade runc-<VERSION_BEFORE_1.4.0> sudo dnf versionlock add runc
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41579?

runc: upgrade to 1.3.6, 1.4.3. Exact commands for each OS are on this page.

Is CVE-2026-41579 being exploited?

CVE-2026-41579 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41579 affect?

CVE-2026-41579 affects runc. Severity is low (CVSS 3.3). 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

How urgent is CVE-2026-41579?

Priority 19/100. On your watchlist

Software pages

containerd and runc vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.