CVE-2026-79705
Podman: buildah: buildah/copier: directory escape via crafted tar symlinks when used outside buildah by non-root callers
What happened?
A flaw was found in the buildah/copier Go package. When used outside of Buildah by a non-root caller, a crafted tar archive containing malicious symlinks can escape the target extraction directory and create files outside the intended destination. Buildah itself uses chroot hardening and is not affected.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| podman-mainRed Hat | unaffected: 6.1.3-1.hum1 to < * | See vendor advisory |
| ansible-automation-platform-24/eda-controller-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-25/eda-controller-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-26/eda-controller-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-27/eda-controller-rhel9Red Hat | Default status: affected | See vendor advisory |
| python3.11-podmanRed Hat | Default status: affected | See vendor advisory |
| python3.12-podmanRed Hat | Default status: affected | See vendor advisory |
| python3x-podmanRed Hat | Default status: affected | See vendor advisory |
| python-podmanRed Hat | Default status: affected | See vendor advisory |
| buildahRed Hat | Default status: affected | See vendor advisory |
| podmanRed Hat | Default status: affected | See vendor advisory |
| python-podmanRed Hat | Default status: affected | See vendor advisory |
| rhel10/buildahRed Hat | Default status: affected | See vendor advisory |
| ubi10/buildahRed Hat | Default status: affected | See vendor advisory |
| ubi10/podmanRed Hat | Default status: affected | See vendor advisory |
| container-tools:rhel8/buildahRed Hat | Default status: affected | See vendor advisory |
| container-tools:rhel8/podmanRed Hat | Default status: affected | See vendor advisory |
| ubi8/buildahRed Hat | Default status: affected | See vendor advisory |
| ubi8/podmanRed Hat | Default status: affected | See vendor advisory |
| buildahRed Hat | Default status: affected | See vendor advisory |
| podmanRed Hat | Default status: affected | See vendor advisory |
| python-podmanRed Hat | Default status: affected | See vendor advisory |
| ubi9/buildahRed Hat | Default status: affected | See vendor advisory |
| ubi9/podmanRed Hat | Default status: affected | See vendor advisory |
| buildahRed Hat | Default status: unaffected | See vendor advisory |
| openshift/ose-rhel-coreos-8Red Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
| podmanRed Hat | Default status: affected | See vendor advisory |
| openshift/ose-rhel-coreos-9Red Hat | Default status: affected | See vendor advisory |
| devspaces/udi-base-rhel10Red Hat | Default status: affected | See vendor advisory |
| devspaces/udi-base-rhel9Red Hat | Default status: affected | See vendor advisory |
| devspaces/udi-rhel9Red Hat | Default status: affected | See vendor advisory |
| container-native-virtualization/ocp-virt-validation-checkup-rhel9Red Hat | Default status: affected | See vendor advisory |
| quay/quay-builder-rhel8Red Hat | Default status: affected | See vendor advisory |
| quay/quay-builder-rhel9Red Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.