---
id: "CVE-2026-93325"
kind: "vulnerability"
aliases: ["CVE-2026-93325"]
title: "Docker Buildx: bake build can skip entitlement consent, reaching outside the working directory"
severity: "high"
cvss: 7.3
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "github.com/docker/buildx", "fixed": ["0.37.2"], "affected": ">= 0.21.0, < 0.37.2", "ecosystem": "go"}]
ecosystems: []
tags: ["bake", "buildx", "ci", "docker", "docker-build", "package"]
not_affected_if: ["default-progress-output", "no-bake-usage", "trusted-build-definitions"]
published_at: "2026-11-03T20:18:19+00:00"
first_seen_at: "2026-11-03T20:49:23+00:00"
updated_at: "2026-11-03T21:02:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93325", "first_seen_at": "2026-11-03T20:49:23+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-03T21:02:16+00:00"}]
---

# Docker Buildx: bake build can skip entitlement consent, reaching outside the working directory

Docker Buildx bake normally asks for explicit permission (via --allow or an interactive prompt) before a build can access files outside the working directory. When run with --progress=rawjson, that consent step is skipped, so a build can reach beyond its directory without approval.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- go:github.com/docker/buildx affected >= 0.21.0, < 0.37.2 fixed 0.37.2

## How to check

- Run `docker buildx version`. Buildx 0.21.0 up to but not including 0.37.2 is affected (the advisory patched-versions field says None, but its text and the release notes name v0.37.2 as the fix).
- Search CI scripts and pipelines for `docker buildx bake` with `--progress=rawjson`, especially on build definitions you do not control. Other progress modes still run the consent gate, so switching away from rawjson is the workaround if you cannot upgrade.

## Fix

Upgrade Docker Buildx to v0.37.2 or later. Bake with --progress=rawjson then rejects ungranted entitlements; grant what you need explicitly with --allow.

## Timeline

- 2026-11-03T20:49:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-93325
- 2026-11-03T21:02:16+00:00 analyst — Read vendor GHSA-gwr2-q96m-6682 and v0.37.2 release notes: affected >=0.21.0, fixed 0.37.2 (GHSA patched: None field contradicts its own text). Sibling GHSA-p54p-jq4x-rc28 fixed in same release. No PoC or exploitation seen; social search skipped (low-profile local issue).

## Documents

- [advisory] Vendor advisory: github.com https://github.com/docker/buildx/security/advisories/GHSA-gwr2-q96m-6682
- [fix] Release notes: github.com https://github.com/docker/buildx/releases/tag/v0.37.2

## From the sources

Buildx bake requires the user to grant entitlements with --allow or an interactive prompt before a build reaches outside the working directory. Under --progress=rawjson that consent step is skipped.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_