{"id":"CVE-2026-47699","aliases":["EUVD-2026-62192","GHSA-84rc-2q4r-45pc"],"status":"published","title":"Confidential Containers Guest Components image-rs: zip-slip-class arbitrary file write via absolute entry path in hardlink fallback","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.","severity":{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.0029,"percentile":0.21718,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-22","CWE-59"],"published":"2026-08-18T21:24:54Z","modified":"2026-10-28T02:30:55Z","products":[{"vendor":"confidential-containers","product":"guest-components"}],"references":[{"url":"https://github.com/confidential-containers/guest-components/security/advisories/GHSA-84rc-2q4r-45pc","tags":["x_refsource_CONFIRM","advisory"]},{"url":"https://github.com/confidential-containers/guest-components/pull/1440","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/confidential-containers/guest-components/pull/1457","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/confidential-containers/guest-components/commit/14fbb711af0b29bb9cad307969d57b0de9b85d7f","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/confidential-containers/guest-components/commit/7cc1bc458973310296e58aedbb15cb7963297bbe","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/confidential-containers/guest-components/releases/tag/v0.20.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47699.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-47699","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-47699","title":"Confidential Containers Guest Components image-rs: zip-slip-class arbitrary file write via absolute entry path in hardlink fallback","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.","status":"published","published":"2026-08-18T21:24:54.28Z","modified":"2026-08-21T19:17:19.41Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-22","CWE-59"],"updated_at":"2026-11-02T13:36:29.327819Z"}],"euvd":[{"id":"EUVD-2026-62192","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.","status":"published","published":"2026-08-18T21:24:54Z","modified":"2026-08-21T19:17:19Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T18:01:37.198267Z"}],"nvd":[{"id":"CVE-2026-47699","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.","status":"published","published":"2026-08-18T22:16:52.127Z","modified":"2026-10-22T17:09:59.477Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-22","CWE-59"],"updated_at":"2026-11-02T14:12:39.620837Z"}],"osv":[{"id":"CVE-2026-47699","title":"Confidential Containers Guest Components image-rs: zip-slip-class arbitrary file write via absolute entry path in hardlink fallback","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.","status":"published","published":"2026-08-18T21:24:54.28Z","modified":"2026-10-28T02:30:55.747090118Z","cvss":[{"version":"3.1","score":6.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-22","CWE-59"],"updated_at":"2026-11-02T15:45:06.231145Z"}]}}