CVE-2026-79699Hinoki check available

Extraction-root replacement via malformed whiteout entry

Published Sep 15, 2026 · Updated Sep 15, 2026

Improper tar extraction in containers/storage allows attackers to replace an extraction destination directory with a file via a crafted layer. The archive.UnpackLayer, ApplyLayer, and ApplyUncompressedLayer paths accept a whiteout entry such as victim/.wh. and process its empty basename as the extraction root rather than rejecting it. Exploitation requires a consumer to unpack an attacker-controlled layer, and the resulting type replacement can corrupt extracted filesystem state.

CVSS severityUnavailable
Unscored
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper tar extraction in containers/storage allows attackers to replace an extraction destination directory with a file via a crafted layer. The archive.UnpackLayer, ApplyLayer, and ApplyUncompressedLayer paths accept a whiteout entry such as victim/.wh. and process its empty basename as the extraction root rather than rejecting it. Exploitation requires a consumer to unpack an attacker-controlled layer, and the resulting type replacement can corrupt extracted filesystem state.

The record

CVE
CVE-2026-79699
Published
Sep 15, 2026
Updated
Sep 15, 2026
Vendor
Red Hat
Product
Red Hat OpenShift Virtualization
Classifications
T1565
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 15, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 15, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

Red Hat · Red Hat OpenShift VirtualizationAffected versions are unavailable in this record.
Red Hat · Red Hat Enterprise Linux 10Affected versions are unavailable in this record.
Red Hat · Red Hat Enterprise Linux 8Affected versions are unavailable in this record.
Red Hat · Red Hat QuayAffected versions are unavailable in this record.
Red Hat · Red Hat Ansible Automation PlatformAffected versions are unavailable in this record.
Red Hat · Red Hat Enterprise Linux 9Affected versions are unavailable in this record.
Red Hat · Red Hat OpenShift Dev SpacesAffected versions are unavailable in this record.
Red Hat · Red Hat Hardened ImagesAffected versions are unavailable in this record.
Red Hat · Red Hat OpenShift Container PlatformAffected versions are unavailable in this record.

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1565Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo