← Back
CVE-2026-61711
Vulnerability in github.com/moby/buildkit (CVE-2026-61711)
Summary
vulnerability in github.com/moby/buildkit (CVE-2026-61711). Risk of unauthorized operations or information disclosure. Exploitable via ``security.insecure``. Mitigation: upgrade to `0.31.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-61711** has been found in github.com/moby/buildkit.
Attackers can target a specific entry point like ``security.insecure`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/moby/buildkit to **0.31.1** or later.
If unsure, ask your IT team or search "github.com/moby/buildkit CVE-2026-61711" on the vendor's site.
CVE-2026-61711 (github.com/moby/buildkit) — CWE-20 /
Attack surface: `security.insecure`
Patched: `0.31.1` — apply immediately
Workaround: Only use BuildKit frontends from trusted providers.
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-20) exists in github.com/moby/buildkit. Attackers reach the vulnerable code path via ``security.insecure`` without authentication.
📍 Affected scope
github.com/moby/buildkit — . Attack surface: `security.insecure`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.31.1**.
🛡️ Workaround
Workaround: Only use BuildKit frontends from trusted providers.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/moby/buildkit' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/moby/buildkit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/moby/buildkit` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Only use BuildKit frontends from trusted providers.パッチが適用されるまでの応急処置として、Only use BuildKit frontends from trusted providers. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/moby/buildkit to 0.31.1ステージング環境で 0.31.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/moby/buildkit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.31.1"}]}]