CVE-2026-93325
Description
A flaw was found in Docker Buildx. This vulnerability allows unauthorized file access and modification due to an authorization bypass in the bake build command. When a build is executed with the raw JSON progress option enabled, the required prompt for user consent before accessing files outside the working directory is skipped. An attacker who convinces a user to run a malicious build configuration with this flag can read or alter files on the host system without authorization.
Statement
Red Hat has evaluated this vulnerability as having an Important severity rating because an authorization bypass allows untrusted build files to access and manipulate host system resources outside the intended project directory, resulting in significant confidentiality and integrity impact. In typical Red Hat deployments, native container toolchains such as Podman and Buildah are used instead of Docker Buildx, confining potential exposure to container images or developer environments that bundle this component. Exploitation is not exposed over a remote network service and requires local user interaction to process a specially crafted build configuration under specific raw progress output conditions.
Mitigation
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce interactive entitlement consent checks and reject ungranted filesystem access when running buildx bake under raw JSON progress: upgrade to Docker Buildx 0.37.2+ (or the fixed Rhceph/Alloy Rhel builds), which explicitly reject ungranted entitlements instead of skipping consent checks when running bake with raw JSON progress, closing malicious bake configuration processed with --progress=rawjson. Until patched, this is a concern on developer and build environments processing untrusted Docker Buildx bake definitions, so avoid running docker buildx bake with the --progress=rawjson flag on untrusted build configurations. As a compensating measure, detect behavioral anomalies such as unexpected host file reads or modifications initiated by the Docker Buildx process via EDR, log file open, read, and write syscalls directed at monitored host paths outside the build working directory using auditd, detect unauthorized sensitive host file reads or writes attempted by the build process using Falco eBPF kernel event rules, and monitor critical host files outside the project directory for unauthorized integrity violations using AIDE. These controls limit blast radius and contain exploitation, but they do not fix the underlying entitlement check authorization bypass defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1001 EDR Agent (Endpoint Detection & Response) (medium)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.3 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | Required | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | High | N/A | N/A |
| Availability Impact | Low | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
Understanding the Weakness (CWE)
Other
Technical Impact: Alter Execution Logic; Unexpected State
By performing actions in an unexpected order, or by omitting steps, an attacker could manipulate the business logic of the product or cause it to enter an invalid state. In some cases, this can also expose resultant weaknesses with security implications.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
