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

CVE-2020-10696 buildah

HIGHFix: containers/buildah#2245

CVE-2020-10696 is a high-severity (CVSS 8.8) Path Traversal vulnerability in github.com/containers/buildah. 2 public exploit references exist, so weaponization risk is real. A fix is available for github.com/containers/buildah — see the affected versions and patch details below.

Path Traversal in Buildah

Also known asGHSA-fx8w-mjvm-hvpcGO-2022-0828
Published
Mar 31, 2020
Updated
Aug 27, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs85th percentile — riskier than 85% 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

CVE-2020-10696 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 377,166 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 path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/containers/buildahall versions1.14.4go get github.com/containers/buildah@v1.14.4
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10696 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 CVE-2020-10696 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2020-10696. 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

While OpenShift Container Platform does include the vulnerable buildah code, it doesn't make use of the vulnerable function. Podman is also included in OpenShift Container Platform, but it isn't used to perform a build, so it has been given a low impact rating. OpenShift Container Platform 3.11 now used podman from…

ProductFixed inAdvisory
Red Hat Enterprise Linux 7 Extrasbuildah-0:1.11.6-11.el7_8RHSA-2020:2116
Red Hat Enterprise Linux 7 Extraspodman-0:1.6.4-18.el7_8RHSA-2020:2117
Red Hat Enterprise Linux 8container-tools:1.0-8020020200420104655.28c38760RHSA-2020:1926
Red Hat Enterprise Linux 8container-tools:2.0-8020020200420175838.28c38760RHSA-2020:1931
Red Hat Enterprise Linux 8container-tools:rhel8-8020020200420180128.28c38760RHSA-2020:1932
Red Hat OpenShift Container Platform 4.1podman-0:1.0.2-4.dev.git96ccc2e.rhaos4.1.el8RHSA-2020:1449
Red Hat OpenShift Container Platform 4.2podman-0:1.4.2-6.rhaos4.2.el8RHSA-2020:1401
Red Hat OpenShift Container Platform 4.3podman-0:1.6.4-10.rhaos4.3.el8RHSA-2020:1396

Frequently Asked Questions

A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.
O3 Security · Impact-Aware SCA

Is CVE-2020-10696 in your dependencies?

O3 Security finds CVE-2020-10696 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2020-10696: buildah (High 8.8) | O3 Security