Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-17106

Vulnerability in github.com/moby/go-archive (CVE-2026-17106)

Summary

Vulnerability in github.com/moby/go-archive (CVE-2026-17106). Risk of unauthorized operations or information disclosure. Exploitable via Unpack. Mitigation: upgrade to 0.3.0 or later.

Original description

The description as published by the source.

moby/go-archive: Crafted tar archive can write outside the extraction directory in github.com/moby/go-archive

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-17106 has been found in github.com/moby/go-archive.
Attackers can target a specific entry point like Unpack over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/moby/go-archive to 0.3.0 or later.
If unsure, ask your IT team or search "github.com/moby/go-archive CVE-2026-17106" on the vendor's site.

CVE-2026-17106 (github.com/moby/go-archive) — CWE-59
Attack surface: Unpack / UnpackLayer / Untar / UntarUncompressed
Patched: 0.3.0 — apply immediately
Workaround: Only extract trusted archives.
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 (CWE-59) exists in github.com/moby/go-archive. Attackers reach the vulnerable code path via Unpack.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/moby/go-archive. Attack surface: Unpack / UnpackLayer / Untar / UntarUncompressed.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.3.0.

🛡️ Workaround

Workaround: Only extract trusted archives.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/moby/go-archive' . 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. 1
    Identify exposure identify 
    grep -r 'github.com/moby/go-archive' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/moby/go-archive を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Only extract trusted archives.

    パッチが適用されるまでの応急処置として、Only extract trusted archives. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/moby/go-archive to 0.3.0

    ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

go github.com/moby/go-archive
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.3.0"}]}]
Bitnami docker-cli
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"29.7.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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