Vulnerability in golang-github-containers-buildah (DEBIAN-CVE-2026-44517)

Summary

Vulnerability in golang-github-containers-buildah (DEBIAN-CVE-2026-44517). Confidential information can be exposed externally. Mitigation: upgrade to 1.43.2+ds1-1 or later.

Original description

The description as published by the source.

Buildah is a tool that facilitates building OCI images. From 1.38.1 until 1.43.2 and 1.44.0, TempDirForURL in define/types.go does not securely confine Git repository subdirectories to the downloaded build context, and downloadToDirectory and stdinToDirectory can follow a Dockerfile symlink left by a partially extracted tar archive. A malicious server supplying a Git repository or tar archive can cause files outside the build context directory to be included in the context or copied into the build. This issue is fixed in versions 1.43.2 and 1.44.0.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-44517 has been found in golang-github-containers-buildah.
Confidential information can be exposed externally.
What to do: upgrade golang-github-containers-buildah to 1.43.2+ds1-1 or later.
If unsure, ask your IT team or search "golang-github-containers-buildah DEBIAN-CVE-2026-44517" on the vendor's site.

DEBIAN-CVE-2026-44517 (golang-github-containers-buildah)
Attack vector: local / unauthenticated
Patched: 1.43.2+ds1-1 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in golang-github-containers-buildah.

📍 Affected scope

Check the vendor advisory for the affected versions of golang-github-containers-buildah.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 1.43.2+ds1-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang-github-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

1
Identify exposure identify
```
grep -r 'golang-github-containers-buildah' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で golang-github-containers-buildah を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade golang-github-containers-buildah to 1.43.2+ds1-1
```
ステージング環境で 1.43.2+ds1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 golang-github-containers-buildah

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:14 golang-github-containers-buildah

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.43.2+ds1-1"}]}]

References

advisory security-tracker.debian.org