Loading...
Skip to main content

CVE-2024-11218 — Vulnerability in github.com/containers/buildah —...

HIGH

Buildah allows build breakout using malicious Containerfiles and concurrent builds

Published January 21, 2025Updated September 10, 2026Source: osv

Summary

### 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.

Advisory Timeline

  • First published January 21, 2025 (629 days ago).
  • Last revised September 10, 2026 — 596 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/containers/buildah to 1.35.5 or later
go get github.com/containers/buildah@v1.35.5
Go
Update github.com/containers/buildah to 1.37.6 or later
go get github.com/containers/buildah@v1.37.6
Go
Update github.com/containers/buildah to 1.33.12 or later
go get github.com/containers/buildah@v1.33.12
Go
Update github.com/containers/buildah to 1.38.1 or later
go get github.com/containers/buildah@v1.38.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (4)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
github.com/containers/buildah
go
All versions1.35.5
github.com/containers/buildah
go
All versions1.37.6
github.com/containers/buildah
go
All versions1.33.12
github.com/containers/buildah
go
All versions1.38.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-269
    Improper Privilege ManagementMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

References

Frequently Asked Questions

What is CVE-2024-11218?
Buildah allows build breakout using malicious Containerfiles and concurrent builds This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
How do I check if my project is affected by CVE-2024-11218?
CVE-2024-11218 affects github.com/containers/buildah. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2024-11218 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.6

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-5vpc-35f4-r8w6
GO-2025-3414

Related CVEs

  • CVE-2026-107809
    HIGH

    Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

  • CVE-2026-57231
    HIGH

    Podman: Malformed Image can trick podman run into leaking host environment variables into the container

  • CVE-2026-107813
    HIGH

    Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies