# CVE-2026-47699: Path traversal in guest-components

> A crafted OCI image layer allows arbitrary file writes via hardlink fallback, enabling workload owners to escape into the pod virtual machine.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-84rc-2q4r-45pc

## What is CVE-2026-47699?

CVE-2026-47699 is a medium-severity path traversal vulnerability in confidential-containers guest-components, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-47699?


## How do I fix CVE-2026-47699?

No fix has been published for CVE-2026-47699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47699 being exploited?

There is no known exploitation of CVE-2026-47699 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47699 and fix it if it is affected.

What it is: CVE-2026-47699 is a medium-severity path traversal vulnerability in confidential-containers guest-components, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47699 in the wild and no public exploit code.

Affected product: confidential-containers guest-components. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47699/ (Markdown: https://insights.sbomify.com/CVE-2026-47699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47699
- OSV: https://osv.dev/vulnerability/CVE-2026-47699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47699/
Summaries are generated and may contain mistakes; the official description above is the record.