CVE-2026-41579

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
3.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.3
EG Score
3.3(medium)
EPSS
12.7%
KEV
Not listed

Published

June 22, 2026

Last Modified

July 2, 2026

References (2)

Vendor Advisories for CVE-2026-41579(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/opencontainers/runc—1.5.0-rc.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 22:51 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-01 22:22 UTCEG score recompute
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-07-01 03:20 UTCNVD updateseverity → LOW
  11. 2026-06-28 21:36 UTCEG score recompute
  12. 2026-06-25 21:06 UTCEG score recompute
  13. 2026-06-22 20:36 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-41579?
CVE-2026-41579 is a low vulnerability published on June 22, 2026. 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…
When was CVE-2026-41579 disclosed?
CVE-2026-41579 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41579 actively exploited?
CVE-2026-41579 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41579?
CVE-2026-41579 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-41579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41579, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41579

Explore →

Is Your Infrastructure Affected by CVE-2026-41579?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs