Path Traversal in github.com/containers/buildah (CVE-2026-44517)
Summary
Path traversal in github.com/containers/buildah (CVE-2026-44517). Confidential information can be exposed externally. Exploitable via add. Mitigation: upgrade to 1.43.2 or later.
Original description
The description as published by the source.
Impact
When processing a build contexts or add/copy instructions, a malicious server serving a Git repository or a tar archive file can cause files outside of the build context directory to be included in the build context or copied into the build.
Patches
Fixed in Buildah 1.44 and 1.43.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44517 has been found in github.com/containers/buildah.
Attackers can target a specific entry point like add over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade github.com/containers/buildah to 1.43.2 or later.
If unsure, ask your IT team or search "github.com/containers/buildah CVE-2026-44517" on the vendor's site.
CVE-2026-44517 (github.com/containers/buildah) — CWE-22 / CVSS v3 6.3
Attack vector: local / unauthenticated
Attack surface: add / copy
Patched: 1.43.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/containers/buildah. Attackers reach the vulnerable code path via add without authentication.
Check the vendor advisory for the affected versions of github.com/containers/buildah. Attack surface: add / copy.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 1.43.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/containers/buildah' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/containers/buildah' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/containers/buildahを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/containers/buildah to 1.43.2ステージング環境で 1.43.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-44517 podman Fixed in: 5.8.3-r0
- Debian DEBIAN-CVE-2026-44517 golang-github-containers-buildah
- Ubuntu UBUNTU-CVE-2026-44517 golang-github-containers-buildah