Vulnerability in github.com/docker/docker (CVE-2026-42306)
Summary
Vulnerability in github.com/docker/docker (CVE-2026-42306). Data can be tampered with by attackers. Mitigation: upgrade to 2.0.0-beta.14 or later.
Original description
The description as published by the source.
A race condition in the Docker daemon allows an attacker to redirect bind mounts to arbitrary host paths during a "docker cp" operation.
The affected code is in the daemon package, specifically the openContainerFS method. This is daemon-owned, Linux-specific code and is not intended for external use as a Go library.
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-42306 has been found in github.com/docker/docker.
Data can be tampered with by attackers. CVSS score: 7.2/10.
What to do: upgrade github.com/docker/docker to 2.0.0-beta.14 or later.
If unsure, ask your IT team or search "github.com/docker/docker CVE-2026-42306" on the vendor's site.
CVE-2026-42306 (github.com/docker/docker) — CWE-367 / CVSS v3 7.2
Attack vector: local
Patched: 2.0.0-beta.14 — 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.
A vulnerability (CWE-367) exists in github.com/docker/docker.
Check the vendor advisory for the affected versions of github.com/docker/docker.
Severity: High (CVSS 7.2/10). Data can be tampered with by attackers.
Update to 2.0.0-beta.14.
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/docker/docker' . 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/docker/docker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/docker/dockerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/docker/docker to 2.0.0-beta.14ステージング環境で 2.0.0-beta.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-42306 docker Fixed in: 29.5.1-r0
- Debian DEBIAN-CVE-2026-42306 docker.io
- Ubuntu UBUNTU-CVE-2026-42306 docker.io
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com