CVE-2026-121522

Possible panic from Git source resolver

publishedCWE-476

In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by that daemon. The issue is fixed in v0.34.2.

Technical severity6.7 mediumCVSS 4.0 · CNA: Docker

Published2026-11-03Source updated 2026-11-06

Collected2026-11-073 attributed sources

Fixes and workarounds

Fix

Upgrade BuildKit to v0.34.2 or later.

Source: CNA: Docker

Workaround

Avoid untrusted build definitions. Only specific builds using Git dependencies trigger this issue.

Source: CNA: Docker

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
BuildKit moby `github.com/moby/buildkit`	≥ 0.26.0; < 0.34.2 (affected, semver) Other versions: unaffected	CNA: Docker

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / score	Vector	Authority
4.0 / 6.7 medium	`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`	CNA: Docker
4.0 / 6.7 medium	`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X`	NVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

https://github.com/moby/buildkit/security/advisories/GHSA-2fqp-xg6f-v7gjCNA: Docker · vendor-advisory
https://github.com/moby/buildkit/security/advisories/GHSA-2fqp-xg6f-v7gj[email protected]

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide