CVE-2024-11218: Buildah Package Vulnerability Leading to Build Breakout
Summary
CVE-2024-11218: Buildah allows build breakout using malicious Containerfiles and concurrent builds in github.com/containers/buildah. Affects github.com/containers/buildah across 4 version ranges.
< 1.33.12
>= 1.35.0, < 1.35.5
>= 1.37.0, < 1.37.6
>= 1.38.0, < 1.38.1
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Also tracked for
- golang-github-containers-buildah · Debian:11
The same CVE-2024-11218 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Buildah is a tool that facilitates the building of container images. It allows users to create and manage container images without requiring a full container runtime. Its key features include support for multiple image formats, integration with various container registries, and the ability to build images from Dockerfiles or Containerfiles. However, it has been identified that Buildah is susceptible to vulnerabilities that can lead to build breakout, particularly when using malicious Containerfiles in concurrent builds.
Vulnerability Detail
The vulnerability in Buildah arises from its handling of Containerfiles during concurrent builds. Malicious Containerfiles can exploit this behavior, allowing unauthorized access to the host filesystem or other unintended consequences. This could lead to sensitive data exposure or compromise the integrity of the build process. The vulnerability is particularly concerning in environments where multiple builds are executed simultaneously, increasing the risk of exploitation.
How To Fix
Latest published version: v1.43.5 as of 22 Oct 2026
go get github.com/containers/buildah@v1.43.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.33.121.33.12go get github.com/containers/buildah@v1.33.12 -
>= 1.35.0, < 1.35.51.35.5go get github.com/containers/buildah@v1.35.5 -
>= 1.37.0, < 1.37.61.37.6go get github.com/containers/buildah@v1.37.6 -
>= 1.38.0, < 1.38.11.38.1go get github.com/containers/buildah@v1.38.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, avoid running concurrent builds that utilize untrusted or malicious Containerfiles. Implement strict validation and sanitization of Containerfiles before use to mitigate the risk of exploitation.
Conclusion
The Buildah package has a critical vulnerability that can lead to build breakout when using malicious Containerfiles in concurrent builds. It is essential to update to the latest patched versions to mitigate this risk. Users are also encouraged to implement workarounds and validate Containerfiles to enhance security.
See every vulnerability recorded for github.com/containers/buildah →
FAQ
The vulnerability allows build breakout using malicious Containerfiles during concurrent builds, potentially leading to unauthorized access to the host filesystem.
You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors open-source vulnerabilities in real-time.
The patched versions of Buildah are 1.33.12, 1.35.5, 1.37.6, and 1.38.1.
If an immediate update is not possible, avoid using untrusted Containerfiles and refrain from running concurrent builds.
More information can be found in the vulnerability database at https://pkg.go.dev/vuln/GO-2025-3414.
Related vulnerabilities
Recent vulnerabilities recorded for github.com/containers/buildah.
