NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Buildah allows build breakout using malicious Containerfiles and concurrent buildsGHSA-5vpc-35f4-r8w6

HIGHFix: containers/buildah#5918

GHSA-5vpc-35f4-r8w6 is a high-severity (CVSS 8.6) Improper Privilege Management vulnerability in github.com/containers/buildah. A fix is available for github.com/containers/buildah — see the affected versions and patch details below.

Also known asCVE-2024-11218GO-2025-3414
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5vpc-35f4-r8w6.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk
0.00%0.29%0.58%0.86%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐹github.com/containers/buildah🐹github.com/containers/buildah🐹github.com/containers/buildah🐹github.com/containers/buildah

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/containers/buildah≥ 1.38.0&&< 1.38.11.38.1go get github.com/containers/buildah@v1.38.1
🐹Gogithub.com/containers/buildah≥ 1.37.0&&< 1.37.61.37.6go get github.com/containers/buildah@v1.37.6
🐹Gogithub.com/containers/buildah≥ 1.35.0&&< 1.35.51.35.5go get github.com/containers/buildah@v1.35.5
🐹Gogithub.com/containers/buildahall versions1.33.12go get github.com/containers/buildah@v1.33.12

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/buildah, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/containers/buildah to 1.38.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5vpc-35f4-r8w6 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability marked as important severity rather than moderate because it allows a malicious Containerfile to exploit the `--mount` flag in `RUN` instructions to directly interact with the build host's filesystem. By leveraging this, an attacker can gain unauthorized access to sensitive files or inject malicious…

Workaround published by Red Hat
Mandatory access controls should limit the access of the process performing the build, on systems where they are enabled. SELinux enforces strict access controls by confining the build process (e.g., Podman) to specific domains like container_t. This prevents unauthorized access to sensitive host files and directories, even if a malicious Containerfile tries to exploit the --mount flag.
Source: Red Hat security advisory for GHSA-5vpc-35f4-r8w6 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 8container-tools:rhel8-8100020250124120243.afee755dRHSA-2025:1372
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportcontainer-tools:rhel8-8060020250203202123.3b538bd8RHSA-2025:1207
Red Hat Enterprise Linux 8.8 Extended Update Supportcontainer-tools:rhel8-8080020250207173112.0f77c1b7RHSA-2025:1275
Red Hat Enterprise Linux 9podman-4:5.2.2-13.el9_5RHSA-2025:0922
Red Hat Enterprise Linux 9buildah-2:1.37.6-1.el9_5RHSA-2025:0923
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutionspodman-2:4.2.0-6.el9_0RHSA-2025:1186
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutionsbuildah-1:1.26.9-1.el9_0RHSA-2025:1187
Red Hat Enterprise Linux 9.2 Extended Update Supportbuildah-1:1.29.5-1.el9_2RHSA-2025:1295

Frequently Asked Questions

### 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 unprivi
O3 Security · Impact-Aware SCA

Is GHSA-5vpc-35f4-r8w6 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Buildah allows build breakout using malicious…