Skip to content
statance
MenuClose
medium · CVSS 4.5

CVE-2026-79705

Podman: buildah: buildah/copier: directory escape via crafted tar symlinks when used outside buildah by non-root callers

Published 15 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
podman-mainRed Hatunaffected: 6.1.3-1.hum1 to < *See vendor advisory
ansible-automation-platform-24/eda-controller-rhel8Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-25/eda-controller-rhel8Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-26/eda-controller-rhel9Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-27/eda-controller-rhel9Red HatDefault status: affectedSee vendor advisory
python3.11-podmanRed HatDefault status: affectedSee vendor advisory
python3.12-podmanRed HatDefault status: affectedSee vendor advisory
python3x-podmanRed HatDefault status: affectedSee vendor advisory
python-podmanRed HatDefault status: affectedSee vendor advisory
buildahRed HatDefault status: affectedSee vendor advisory
podmanRed HatDefault status: affectedSee vendor advisory
python-podmanRed HatDefault status: affectedSee vendor advisory
rhel10/buildahRed HatDefault status: affectedSee vendor advisory
ubi10/buildahRed HatDefault status: affectedSee vendor advisory
ubi10/podmanRed HatDefault status: affectedSee vendor advisory
container-tools:rhel8/buildahRed HatDefault status: affectedSee vendor advisory
container-tools:rhel8/podmanRed HatDefault status: affectedSee vendor advisory
ubi8/buildahRed HatDefault status: affectedSee vendor advisory
ubi8/podmanRed HatDefault status: affectedSee vendor advisory
buildahRed HatDefault status: affectedSee vendor advisory
podmanRed HatDefault status: affectedSee vendor advisory
python-podmanRed HatDefault status: affectedSee vendor advisory
ubi9/buildahRed HatDefault status: affectedSee vendor advisory
ubi9/podmanRed HatDefault status: affectedSee vendor advisory
buildahRed HatDefault status: unaffectedSee vendor advisory
openshift/ose-rhel-coreos-8Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory
podmanRed HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory
devspaces/udi-base-rhel10Red HatDefault status: affectedSee vendor advisory
devspaces/udi-base-rhel9Red HatDefault status: affectedSee vendor advisory
devspaces/udi-rhel9Red HatDefault status: affectedSee vendor advisory
container-native-virtualization/ocp-virt-validation-checkup-rhel9Red HatDefault status: affectedSee vendor advisory
quay/quay-builder-rhel8Red HatDefault status: affectedSee vendor advisory
quay/quay-builder-rhel9Red HatDefault status: affectedSee 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.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. 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.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed