HighGHSA-5vpc-35f4-r8w6CVE-2024-11218GO-2025-3414

Buildah allows build breakout using malicious Containerfiles and concurrent builds

Published 21 Jan 2025 · Updated 10 Sept 2026

Is your project on an affected github.com/containers/buildah?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.38.0 <1.38.1
Fixed in
1.38.1
Update to the fixed version for your release line, for example:go get github.com/containers/buildah@v1.38.1
Affected
>=1.37.0 <1.37.6
Fixed in
1.37.6
Update to the fixed version for your release line, for example:go get github.com/containers/buildah@v1.37.6
Affected
>=1.35.0 <1.35.5
Fixed in
1.35.5
Update to the fixed version for your release line, for example:go get github.com/containers/buildah@v1.35.5
Affected
<1.33.12
Fixed in
1.33.12
Update to the fixed version for your release line, for example:go get github.com/containers/buildah@v1.33.12

Details

Impact

With careful use of the --mount flag in RUN instructions in Containerfiles, and by using either multi-stage builds with use of concurrently-executing build stages (e.g., using the --jobs CLI flag) or multiple separate but concurrently-executing builds, a malicious Containerfile can be used to expose content from the build host to the command being run using the RUN instruction. This can be used to read or write contents using the privileges of the process which is performing the build. When that process is a root-owned podman system service which is provided for use by unprivileged users, this includes the ability to read and write contents which the client should not be allowed to read and write, including setuid executables in locations where they can be later accessed by unprivileged users.

Patches

Patches have been merged to the main branch, and will be added to upcoming releases on the release-1.38, release-1.37, release-1.35, and release-1.33 branches.

This addressed a number of Jira cards, but primarily https://issues.redhat.com/browse/RHEL-67616 and https://issues.redhat.com/browse/RHEL-67618, which were then vendored into Podman and backported into olde rbranches.

Workarounds

Mandatory access controls should limit the access of the process performing the build, on systems where they are enabled.

Is GHSA-5vpc-35f4-r8w6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/containers/buildah, and gives you the command that fixes it.

More advisories for github.com/containers/buildah

  • LowCVE-2026-44517Build breakout using malicious Containerfile or Git HTTP server in github.com/containers/buildah · 27 Jul 2026
  • MediumCVE-2026-44517Build breakout using malicious Containerfile and Git Smart HTTP server or GitHub release tar archive · 22 Jun 2026
  • LowCVE-2024-9675Buildah allows arbitrary directory mount in github.com/containers/buildah · 11 Oct 2024
  • LowCVE-2024-9407Improper Input Validation in Buildah and Podman in github.com/containers/buildah · 9 Oct 2024
  • MediumCVE-2024-9675Buildah allows arbitrary directory mount · 9 Oct 2024
  • MediumCVE-2024-9407Improper Input Validation in Buildah and Podman · 1 Oct 2024
All 17 advisories for github.com/containers/buildah

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.