Vulnerability in github.com/moby/buildkit (CVE-2026-61712)
Summary
Vulnerability in github.com/moby/buildkit (CVE-2026-61712). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.31.1 or later.
Original description
The description as published by the source.
BuildKit has a possible runtime DoS via unbounded group parsing in github.com/moby/buildkit
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-61712 has been found in github.com/moby/buildkit.
Risk of unauthorized operations or information disclosure.
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-61712" on the vendor's site.
CVE-2026-61712 (github.com/moby/buildkit) — CWE-770
Patched: 0.31.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.
A vulnerability (CWE-770) exists in github.com/moby/buildkit.
Check the vendor advisory for the affected versions of github.com/moby/buildkit.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.31.1.
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/moby/buildkit' . 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/moby/buildkit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/moby/buildkitを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/moby/buildkit to 0.31.1ステージング環境で 0.31.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-61712
References
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com