{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47699 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-47699 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-47699 in the wild and no public exploit code.\n\nAffected product: confidential-containers guest-components. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47699/ (Markdown: https://insights.sbomify.com/CVE-2026-47699/index.md)","id":"CVE-2026-47699","markdown":"https://insights.sbomify.com/CVE-2026-47699/index.md","name":"CVE-2026-47699","record":{"aliases":["GHSA-84rc-2q4r-45pc"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Confidential Containers guest","requires_auth":"low_privilege","summary":"A crafted OCI image layer allows arbitrary file writes via hardlink fallback, enabling workload owners to escape into the pod virtual machine.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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(\u0026entry_rel). Rust Path::join replaces the base when entry_rel is an absolute tar entry path, so fs::hard_link(\u0026src_canon, \u0026dst_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in guest-components","id":"CVE-2026-47699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"OpenTelemetry Operator: ServiceMonitor bearerTokenFile reads arbitrary local file and sends contents as bearer auth","id":"CVE-2026-47701"},"packages":[],"prev":{"headline":"vm2: Sandbox Breakout Using Dangerous Host Proto Mutators","id":"CVE-2026-47698"},"products":["guest-components"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["confidential-containers"]},"summary":"A crafted OCI image layer allows arbitrary file writes via hardlink fallback, enabling workload owners to escape into the pod virtual machine.","url":"https://insights.sbomify.com/CVE-2026-47699/"}