# CVE-2026-93325: Docker Buildx bake entitlement consent bypass with --progress=rawjson

Source: https://junglewise.ai/threats/cve-2026-93325-buildx-bake-requires-the-user-to-grant-entitlements-with-allow-or  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-93325 · Severity: info · Published 2026-11-03

Docker Buildx is a tool that builds container images. When using the bake command with the --progress=rawjson flag, a security consent check is bypassed that normally requires users to explicitly approve when a build accesses files outside its working directory. An attacker who tricks a user into running bake with untrusted build definitions and this flag could gain unauthorized access to sensitive files on the system.

Technologies: [Docker Buildx](https://junglewise.ai/threats/technologies/buildx). Vendors: [Docker](https://junglewise.ai/threats/vendors/docker).

## Quick answers

**Is CVE-2026-93325 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-93325 being exploited in the wild.

**How severe is CVE-2026-93325?** Informational severity, published 3 November 2026.

**Which products and versions are affected?** Docker Buildx >=0.21.0 before 0.37.2.

**Is there a fix for CVE-2026-93325?** Yes: fixed in v0.37.2. Until then: Do not run bake with --progress=rawjson on untrusted build definitions; use a different progress mode to ensure the consent gate is enforced. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-93325 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-93325?** Check whether you run Docker Buildx at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in v0.37.2

Do not run bake with --progress=rawjson on untrusted build definitions; use a different progress mode to ensure the consent gate is enforced.

## Technical details

Buildx bake has a filesystem entitlement consent gate that prompts users or requires the --allow flag before builds can access files outside the working directory. Under --progress=rawjson mode, this consent check is skipped, allowing unauthorized filesystem access. The vulnerability affects versions >=0.21.0 and requires the attacker to convince a user to run bake with an untrusted definition and the --progress=rawjson flag; it was fixed in v0.37.2.

## Affected products

- Docker Buildx >=0.21.0 before 0.37.2

## Timeline

- 2026-09-30: disclosed
- 2026-09-30: patched

## References

- [https://github.com/docker/buildx/releases/tag/v0.37.2](https://github.com/docker/buildx/releases/tag/v0.37.2)
- [https://github.com/docker/buildx/security/advisories/GHSA-gwr2-q96m-6682](https://github.com/docker/buildx/security/advisories/GHSA-gwr2-q96m-6682)

## Related threats

- [Docker Buildx filesystem entitlement bypass in Bake](https://junglewise.ai/threats/cve-2026-121542-in-docker-buildx-versions-v0-19-0-through-v0-38-0-an-untrusted)
- [Docker Buildx entitlements bypass in multi-target builds](https://junglewise.ai/threats/cve-2026-121541-in-docker-buildx-versions-v0-19-0-through-v0-38-0-an-untrusted)
- [Docker Buildx Bake fs.read approval bypass for filesystem inputs](https://junglewise.ai/threats/cve-2026-103433-docker-buildx-bake-does-not-request-the-expected-fs-read)