CVE-2026-121541

Bake filesystem path entitlements approval can be skipped in some multi-target builds

publishedCWE-863

In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition that builds multiple targets together may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, filesystem paths from some targets are not verified against the approved entitlements. Users who run untrusted Bake definitions may be affected. The issue is fixed in v0.38.1.

Technical severity5.6 mediumCVSS 4.0 · CNA: Docker

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

Collected2026-11-073 attributed sources

Fixes and workarounds

Fix

Upgrade Docker Buildx to v0.38.1 or later.

Source: CNA: Docker

Workaround

Run only trusted Bake definitions until upgrading. Check that Bake definitions do not contain suspicious paths outside trusted directories.

Source: CNA: Docker

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
Docker Buildx Docker	≥ 0.19.0; < 0.38.1 (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 / 5.6 medium	`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`	CNA: Docker
4.0 / 5.6 medium	`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/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/docker/buildx/security/advisories/GHSA-xg6v-cv2h-2w5hCNA: Docker · vendor-advisory
https://github.com/docker/buildx/security/advisories/GHSA-xg6v-cv2h-2w5h[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