LowGO-2026-5116CVE-2026-44517GHSA-49p4-px3h-rq49
Build breakout using malicious Containerfile or Git HTTP server in github.com/containers/buildah
Published 27 Jul 2026 · Updated 27 Jul 2026
Is your project on an affected github.com/containers/buildah?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=1.38.1
- Fixed in
- No fix released
Details
Buildah allows a build-time breakout when using a malicious Containerfile or a malicious Git HTTP server. A crafted Git URL or Containerfile can cause Buildah to access files outside of the build context during an ADD or COPY operation.
Is GO-2026-5116 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-2024-11218Buildah allows build breakout using malicious Containerfiles and concurrent builds in github.com/containers/buildah · 28 Jan 2025
- HighCVE-2024-11218Buildah allows build breakout using malicious Containerfiles and concurrent builds · 21 Jan 2025
- 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
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.