confidential-containers guest-components up to 0.19.x OCI Image Unpacker unpack.rs try_hardlink_fallback path traversal

Summaryinfo

A vulnerability labeled as critical has been found in confidential-containers guest-components up to 0.19.x. This issue affects the function image_rs::stream::unpack::try_hardlink_fallback of the file image-rs/src/stream/unpack.rs of the component OCI Image Unpacker. Such manipulation leads to path traversal. This vulnerability is documented as CVE-2026-47699. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in confidential-containers guest-components up to 0.19.x. It has been rated as critical. Affected by this issue is the function image_rs::stream::unpack::try_hardlink_fallback of the file image-rs/src/stream/unpack.rs of the component OCI Image Unpacker. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-47699 since 05/19/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.

Upgrading to version 0.20.0 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Virtualization Software

Vendor

• confidential-containers

Name

• guest-components

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19

Website

• Product: https://github.com/confidential-containers/guest-components/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion