Skip to content
Fencer Intel
medium 6.3

CVE-2026-44517 json

Buildah: Build breakout using malicious Containerfile and Git Smart HTTP server or GitHub release tar archive

published 4mo ago modified 28d ago also EUVD-2026-64141 , GHSA-49p4-px3h-rq49 , GO-2026-5116

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

Buildah is a tool that facilitates building OCI images. From 1.38.1 until 1.43.2 and 1.44.0, TempDirForURL in define/types.go does not securely confine Git repository subdirectories to the downloaded build context, and downloadToDirectory and stdinToDirectory can follow a Dockerfile symlink left by a partially extracted tar archive. A malicious server supplying a Git repository or tar archive can cause files outside the build context directory to be included in the context or copied into the build. This issue is fixed in versions 1.43.2 and 1.44.0.

Patch / fix

  • go github.com/containers/buildah 1.43.2
  • buildah_project buildah 1.43.2
  • golang-github-containers-buildah Debian 14 1.43.2+ds1-1

debian advisories DEBIAN-CVE-2026-44517

  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260727T201416-160000.1.1

suse advisories SUSE-SU-2026:23216-1SUSE-SU-2026:23227-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260727T201416-160000.1.1

opensuse advisories openSUSE-SU-2026:21551-1

  • podman Alpine 3.24 5.8.3-r0

alpine advisories ALPINE-CVE-2026-44517

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-44517 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-44517 updated cvss 6.3

github.com/containers/buildah: Buildah: Build breakout via malicious Git repository or tar archive

  • Red Hat Certification Program for Red Hat Enterprise Linux 9 rhcertification/redhat-certification-system-ai-10 Red Hat Enterprise Linux 9 podman, buildah, podman-tests, ubi9/buildah, buildah-tests, podman-docker, +6 more Red Hat Enterprise Linux 10 podman 5.8.2-5.el10_2, buildah 1.43.1-4.el10_2 Red Hat OpenShift Container Platform 4 podman, podman-tests, podman-docker, podman-remote, podman-gvproxy, podman-plugins, +7 more Red Hat OpenShift Container Platform 5 openshift5/microshift-bootc-rhel10, openshift5/ose-docker-builder-rhel9, openshift5/ose-machine-config-rhel9-operator Red Hat OpenShift Dev Spaces devspaces/udi-rhel9, devspaces/udi-base-rhel9, devspaces/udi-base-rhel10
    +2 more products
    Red Hat OpenStack Platform 18.0 rhoso-operators/prometheus-podman-exporter-rhel9 Red Hat Quay 3 quay/quay-builder-rhel8, quay/quay-builder-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 8 conmon, podman, buildah, podman-tests, buildah-tests, podman-docker, +5 more Red Hat Enterprise Linux 9 conmon Red Hat Hardened Images buildah 1.43.1-4.el10_2 Red Hat OpenShift Container Platform 4 cri-o, conmon, openshift4/ose-docker-builder
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
GitHub 3.1 6.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/containers/buildah
>=1.38.1, <1.43.2
>=1.38.1
1.43.2

Affected products

  • containers buildah

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.