Live › vulnerability › CVE-2026-93325
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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 20:49 UTC. All times on this page are UTC.
Teams running docker buildx bake, version 0.21.0 to before 0.37.2, with --progress=rawjson. In that mode the --allow / interactive consent check is skipped, so a build definition can reach files outside the working directory without approval. CI pipelines that read bake files from untrusted sources (PRs, third-party repos) matter most. You can skip it if you do not use bake, use other progress modes, or only build trusted definitions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/docker/buildx | go | >= 0.21.0, < 0.37.2 | 0.37.2 |
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).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.v0.37.2 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-93325")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.