Bake filesystem entitlement consent is skipped under --progress=rawjson in Docker Buildx
Docker Buildx 0.21.0 and later, before 0.37.2, skips the filesystem entitlement consent prompt when Bake runs with --progress=rawjson. Fixed in 0.37.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.37.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are Buildx 0.21.0 and later, since the rawjson branch skipped the consent prompt from v0.21.0. Bake is run with --progress=rawjson.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach17/20Affects Docker (a widely deployed server, runtime, framework or database)
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
CVE-2026-93325 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects Docker Buildx; fixed in 0.37.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.37.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Docker Buildx's "bake" command, which runs builds defined in configuration files, can be affected. When the rawjson progress output option is used, it skips the prompt that asks for user approval before a build accesses files outside the working directory, so such access can happen without the user's consent.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Affected versions are Buildx 0.21.0 and later, since the rawjson branch skipped the consent prompt from v0.21.0. Bake is run with --progress=rawjson.Upgrade to a fixed version: 0.37.2.
Workaround: Do not run bake with --progress=rawjson on untrusted definitions; another progress mode runs the consent gate.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- github.com/docker/buildx
From 0.21.0 · fixed in 0.37.2
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-93325
Is CVE-2026-93325 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Under --progress=rawjson, Bake skips the consent step that normally asks before a build is granted filesystem entitlements. The stated impact is code execution in the context of the current user.Source: github.com, zerodayinitiative.com
Which versions are affected by CVE-2026-93325?
github.com/docker/buildx: from 0.21.0 before 0.37.2.Source: cve.now feed data
Am I affected, and how do I check?
Buildx versions from 0.21.0 up to the fix are in scope when Bake runs with --progress=rawjson. To check, run docker buildx version and compare it with 0.37.2, and check whether your bake commands use --progress=rawjson.Source: github.com, zerodayinitiative.com
How do I fix CVE-2026-93325?
Upgrade Docker Buildx to v0.37.2 or later, which contains the fix. Until you upgrade, avoid running bake with --progress=rawjson on untrusted definitions.Source: github.com, zerodayinitiative.com