CVE-2026-79699

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreHIGH confidence

Score 4.4 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

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

A flaw was found in the containers/storage library. A crafted tar archive containing a malicious whiteout header (e.g. victim/.wh.) can cause the extraction destination directory to be replaced with an arbitrary file when processed by storage/pkg/archive.UnpackLayer, ApplyLayer, or ApplyUncompressedLayer.

CVSS v3
4.4
EG Score
4.4(high)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat.
redhat

2523408 – (CVE-2026-79699) CVE-2026-79699 podman: buildah: skopeo: containers/storage: Malicious tar whiteout header allows replacement of extraction destination directory

https://bugzilla.redhat.com/show_bug.cgi?id=2523408
redhat Patch Available

CVE-2026-79699 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-79699

Vendor Advisories for CVE-2026-79699(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 17× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 20:55 UTCEG score recompute
  3. 2026-09-19 20:55 UTCGHSA enrichment
  4. 2026-09-18 20:12 UTCEG score recompute
  5. 2026-09-18 20:12 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-17 19:27 UTCEG score recompute
  8. 2026-09-17 19:27 UTCGHSA enrichment
  9. 2026-09-17 18:47 UTCEG score recompute
  10. 2026-09-17 18:47 UTCGHSA enrichment
  11. 2026-09-16 19:57 UTCGHSA enrichment
  12. 2026-09-16 18:14 UTCEG score recompute
  13. 2026-09-16 18:14 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-15 17:32 UTCEG score recompute
  16. 2026-09-15 16:33 UTCEG score recompute
  17. 2026-09-15 16:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79699?
CVE-2026-79699 is a medium vulnerability published on September 15, 2026. A flaw was found in the containers/storage library. A crafted tar archive containing a malicious whiteout header (e.g. victim/.wh.) can cause the extraction destination directory to be replaced with an arbitrary file when processed by storage/pkg/archive.UnpackLayer, ApplyLayer, or…
When was CVE-2026-79699 disclosed?
CVE-2026-79699 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79699 actively exploited?
CVE-2026-79699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-79699?
CVE-2026-79699 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-79699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79699, 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

Explore the affected products and dependency analysis for CVE-2026-79699

Explore →

Is Your Infrastructure Affected by CVE-2026-79699?

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

Start Free Scan →Browse All CVEs