cve.bz

CVE-2026-79699 Link Following

4.4 mediumEPSS 0.2%

Medium (4.4). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

4.4 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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; 14th 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-09-17. 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-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-79699 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-79699?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-79699?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-79699 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-containers-storageno fix listedDEBIAN-CVE-2026-79699
Ubuntu20.04:LTS, 24.04:LTS, 26.04:LTS and 2 moregolang-github-containers-storageno fix listedUBUNTU-CVE-2026-79699
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 9 moreskopeo1.14.4-150300.11.25.1SUSE-SU-2026:5193-1
openSUSETumbleweedpodman6.1.2-1.1openSUSE-SU-2026:12068-1
openSUSETumbleweedskopeo1.24.0-2.1openSUSE-SU-2026:12478-1
Alpinev3.24podman5.8.8-r0ALPINE-CVE-2026-79699
Azure Linux3buildahno fix listedAZL-103062
Azure Linux3containerized-data-importerno fix listedAZL-103140
Azure Linux3cri-ono fix listedAZL-103071
Azure Linux3libcontainers-commonno fix listedAZL-103227
Azure Linux3moby-engineno fix listedAZL-108396
Azure Linux3podmanno fix listedAZL-103089
Azure Linux3skopeono fix listedAZL-103269
Alpaquitastreampodman6.1.3-r0BELL-CVE-2026-79699

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

Red Hat container tools are not directly affected by this flaw, which primarily impacts external applications that directly call the containers/storage library API. Successful exploitation requires processing a specially crafted tar archive containing a malicious whiteout header, leading to the replacement of an extraction destination directory.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/eda-controller-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/eda-controller-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/eda-controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/eda-controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2python3.11-podmanFix deferred
Red Hat Ansible Automation Platform 2python3.12-podmanFix deferred
Red Hat Ansible Automation Platform 2python3x-podmanFix deferred
Red Hat Ansible Automation Platform 2python-podmanFix deferred
Red Hat Enterprise Linux 10buildahFix deferred
Red Hat Enterprise Linux 10podmanFix deferred
Red Hat Enterprise Linux 10skopeoFix deferred
Red Hat Enterprise Linux 8buildahFix deferred
Red Hat Enterprise Linux 8podmanFix deferred
Red Hat Enterprise Linux 8skopeoFix deferred
Red Hat Enterprise Linux 9buildahFix deferred
Red Hat Enterprise Linux 9podmanFix deferred
Red Hat Enterprise Linux 9python-podmanFix deferred
Red Hat Enterprise Linux 9rhel9/buildahFix deferred
Red Hat Enterprise Linux 9rhel9/podmanFix deferred
Red Hat Enterprise Linux 9rhel9/skopeoFix deferred
12 more in the JSON and on Red Hat's page.

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

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

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

References

Check your stackJSON