Categories
CVE-2026-79705 medium CVSS 4.5

Path Traversal in buildah/copier Go package (CVE-2026-79705)

Summary

Path traversal in buildah/copier Go package (CVE-2026-79705). Data can be tampered with by attackers.

Original description

The description as published by the source.

A flaw was found in the buildah/copier Go package. When used outside of Buildah by a non-root caller, a crafted tar archive containing malicious symlinks can escape the target extraction directory and create files outside the intended destination. Buildah itself uses chroot hardening and is not affected.

Source: NIST National Vulnerability Database 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-79705 has been found in buildah/copier Go package.
Data can be tampered with by attackers. CVSS score: 4.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "buildah/copier Go package CVE-2026-79705" on the vendor's site.

CVE-2026-79705 (buildah/copier Go package) — CWE-22 / CVSS v3 4.5
Attack vector: remote (network-reachable)
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

Path traversal (CWE-22) exists in buildah/copier Go package.

📍 Affected scope

Check the vendor advisory for the affected versions of buildah/copier Go package.

🔥 Severity

Severity: Medium (CVSS 4.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで buildah/copier Go package を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details