Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-586p-749j-fhwp — buildah

MEDIUMFix: containers/buildah@aa67e5d

GHSA-586p-749j-fhwp is a medium-severity (CVSS 4.4) Path Traversal vulnerability in github.com/containers/buildah. A fix is available for github.com/containers/buildah — see the affected versions and patch details below.

Buildah allows arbitrary directory mount

Also known asCVE-2024-9675GO-2024-3186
Published
Oct 9, 2024
Updated
Sep 10, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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-586p-749j-fhwp.

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-586p-749j-fhwp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐹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

A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a RUN instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/containers/buildahall versions1.38.0go get github.com/containers/buildah@v1.38.0

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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-586p-749j-fhwp is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-586p-749j-fhwp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-586p-749j-fhwp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
ProductFixed inAdvisory
Red Hat Enterprise Linux 8container-tools:rhel8-8100020241023085649.afee755dRHSA-2024:8846
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Supportcontainer-tools:rhel8-8060020241028154646.3b538bd8RHSA-2024:8703
Red Hat Enterprise Linux 8.8 Extended Update Supportcontainer-tools:rhel8-8080020241025064551.0f77c1b7RHSA-2024:8707
Red Hat Enterprise Linux 9buildah-2:1.33.10-1.el9_4RHSA-2024:8563
Red Hat Enterprise Linux 9podman-4:4.9.4-16.el9_4RHSA-2024:9051
Red Hat Enterprise Linux 9podman-4:5.2.2-9.el9_5RHSA-2024:9454
Red Hat Enterprise Linux 9buildah-2:1.37.5-1.el9_5RHSA-2024:9459
Red Hat Enterprise Linux 9.0 Extended Update Supportbuildah-1:1.26.8-2.el9_0RHSA-2024:8675

Frequently Asked Questions

A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a `RUN` instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.
O3 Security · Impact-Aware SCA

Is GHSA-586p-749j-fhwp in your dependencies?

O3 Security finds GHSA-586p-749j-fhwp across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-586p-749j-fhwp: buildah (Medium 4.4) | O3 Security