Description
Confidential Containers Guest Components provides guest tools and components for confidential container workloads. From 0.16.0 until 0.20.0, a crafted OCI image layer can make image_rs::stream::unpack::unpack() create a hardlink outside its destination directory. In image-rs/src/stream/unpack.rs, try_hardlink_fallback() validates the hardlink source but computes the destination with destination.join(&entry_rel). Rust Path::join replaces the base when entry_rel is an absolute tar entry path, so fs::hard_link(&src_canon, &dst_entry_abs) can write attacker-controlled content to an arbitrary absolute path. In Confidential Containers the workload owner already controls trusted image content, so the issue is a workload-owner escape into the pod virtual machine rather than a crossing of the image trust boundary, but it may enable access to pod virtual machine capabilities and attestation abuse. This issue is fixed in version 0.20.0.
Published: 2026-08-18
Score: 6.4 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A crafted OCI image layer can cause the unpack routine to create a hardlink that points to an absolute path outside the intended extraction directory. The Path::join logic in image-rs incorrectly treats an absolute tar entry as a base path, allowing this hardlink to write attacker‑controlled data to an arbitrary absolute file on the pod virtual machine. The vulnerability enables a workload owner who already controls image content to escape the image boundary and write files anywhere inside the pod VM, potentially abusing VM capabilities and compromising attestation mechanisms. The primary effect is an arbitrary file write that could lead to privilege escalation or tampering with the virtual machine’s state.

Affected Systems

The vulnerability affects the Confidential Containers Guest Components product, specifically the image‑rs module. All releases from version 0.16.0 up to, but not including, 0.20.0 are vulnerable; version 0.20.0 and later contain the fix.

Risk and Exploitability

The CVSS score of 6.4 indicates a medium severity. The EPSS score is not provided, and the CVE is not listed in CISA KEV, suggesting no known widespread exploitation yet. The attack vector requires an attacker to supply a malicious OCI image layer, which a workload owner can create. Therefore the threat primarily exists to malicious insiders who control image content, enabling them to write files outside the intended extraction context and potentially gain broader access to the pod virtual machine. While the vulnerability does not affect image trust cross‑boundary, it still permits significant compromise of the VM environment if left unpatched.

Generated by OpenCVE AI on August 18, 2026 at 22:48 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Confident Containers Guest Components to version 0.20.0 or later, which removes the hard‑link fallback flaw.
  • If an immediate upgrade is not possible, restrict the guest component’s ability to perform hard‑link operations by disabling the fallback mechanism or enforcing strict validation of tar entry paths to reject absolute paths.
  • Deploy runtime monitoring on the pod VM to detect unexpected hard‑link creation or writes to sensitive directories, and intervene if anomalies are observed.

Generated by OpenCVE AI on August 18, 2026 at 22:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description Confidential Containers Guest Components provides guest tools and components for confidential container workloads. From 0.16.0 until 0.20.0, a crafted OCI image layer can make image_rs::stream::unpack::unpack() create a hardlink outside its destination directory. In image-rs/src/stream/unpack.rs, try_hardlink_fallback() validates the hardlink source but computes the destination with destination.join(&entry_rel). Rust Path::join replaces the base when entry_rel is an absolute tar entry path, so fs::hard_link(&src_canon, &dst_entry_abs) can write attacker-controlled content to an arbitrary absolute path. In Confidential Containers the workload owner already controls trusted image content, so the issue is a workload-owner escape into the pod virtual machine rather than a crossing of the image trust boundary, but it may enable access to pod virtual machine capabilities and attestation abuse. This issue is fixed in version 0.20.0.
Title Confidential Containers Guest Components image-rs: zip-slip-class arbitrary file write via absolute entry path in hardlink fallback
Weaknesses CWE-22
CWE-59
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T21:24:54.280Z

Reserved: 2026-05-19T21:18:20.404Z

Link: CVE-2026-47699

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-18T22:16:52.127

Modified: 2026-08-18T22:16:52.127

Link: CVE-2026-47699

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T23:00:14Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')