Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93320 Overview
CVE-2026-93320 affects Moby BuildKit, the image build toolkit used by Docker and other container platforms. BuildKit may be tricked into performing file actions on special file inodes in locations where it expects regular files. On rootful workers, this behavior can grant unintended access to host device nodes. On other configurations, it can cause operations to block or fail unexpectedly. The flaw is categorized under CWE-441 (Unintended Proxy or Intermediary). Moby addressed the issue in BuildKit v0.33.1.
Critical Impact
A malicious build input can cause BuildKit to operate on device, FIFO, or socket inodes instead of regular files, enabling unintended host device access on rootful workers.
Affected Products
- Moby BuildKit versions prior to v0.33.1
- Container build pipelines that embed BuildKit as a library
- Rootful BuildKit workers invoked by Docker, buildx, or CI/CD runners
Discovery Timeline
- 2026-10-05 - CVE-2026-93320 published to the National Vulnerability Database (NVD)
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-93320
Vulnerability Analysis
BuildKit processes file paths supplied by build instructions, mounts, and context sources. The vulnerability stems from BuildKit treating certain filesystem entries as regular files without validating the inode type. When the target path resolves to a special file such as a character device, block device, FIFO, or Unix socket, BuildKit still performs the requested file action against that inode.
On rootful workers, the BuildKit daemon runs with elevated privileges and can open device nodes under /dev. A crafted build input that steers an operation toward a device inode can therefore reach host devices that the build was never intended to touch. On rootless or non-privileged workers, the mismatch typically causes the operation to block or fail, impacting build integrity and availability.
See the GitHub Security Advisory GHSA-9728-qjrv-2xh2 for the maintainers' technical write-up.
Root Cause
The underlying defect is missing inode type enforcement in file-handling code paths that assume regular files. BuildKit does not stat and reject non-regular inodes before executing the action, so the intermediary logic forwards operations to whatever inode the path resolves to. This matches the CWE-441 pattern of acting as an unintended proxy toward a resource chosen by an untrusted input.
Attack Vector
Exploitation requires local access to a build input that BuildKit will process, and user interaction in the form of running the build. An attacker supplies a Dockerfile, build context, or mount definition that places a special file where a regular file is expected. When a rootful worker executes the build, the file action is applied to the special inode, which may expose host device nodes to the build environment. No network vector is required, and no authentication is needed beyond the ability to submit a build.
No public proof-of-concept exploit is listed in the available references. Refer to the Moby BuildKit v0.33.1 release notes for the corrective behavior.
Detection Methods for CVE-2026-93320
Indicators of Compromise
- BuildKit daemon processes opening device nodes under /dev during image builds
- Unexpected open(), read(), or write() syscalls targeting character or block devices from buildkitd or rootlesskit
- Build logs that reference paths containing FIFOs, sockets, or device files inside the build context
Detection Strategies
- Audit build contexts and Dockerfiles for mknod, mkfifo, or symlinks that resolve to /dev/* entries before submission
- Enable Linux audit rules on BuildKit hosts to log file operations on non-regular inodes performed by the build daemon
- Compare installed BuildKit versions across build nodes against v0.33.1 using software inventory data
Monitoring Recommendations
- Centralize buildkitd process telemetry and alert on syscalls touching /dev, /proc, or /sys during a build
- Monitor CI/CD runners for builds that import unverified contexts or third-party Dockerfiles
- Track the GHSA advisory and NVD entry for updates to affected version ranges and backports
How to Mitigate CVE-2026-93320
Immediate Actions Required
- Upgrade BuildKit to v0.33.1 or later on all build hosts and CI/CD runners
- Rebuild and redistribute downstream tools, such as docker buildx images, that vendor BuildKit as a dependency
- Restrict who can submit builds to rootful BuildKit workers until patching is complete
Patch Information
Moby published the fix in the BuildKit v0.33.1 release. The patched version enforces inode type checks so that operations expecting regular files reject special inodes. Review the GHSA-9728-qjrv-2xh2 advisory for the full list of affected code paths and remediation guidance.
Workarounds
- Run BuildKit in rootless mode where feasible to reduce the privilege available to the build daemon
- Validate build contexts to exclude device files, FIFOs, and sockets before invoking BuildKit
- Isolate build workers from sensitive host devices using namespacing or dedicated build VMs
# Configuration example
# Verify installed BuildKit version and upgrade if below v0.33.1
buildctl --version
docker buildx version
# Example: pin BuildKit image to the patched release in CI
docker buildx create --use \
--name secure-builder \
--driver docker-container \
--driver-opt image=moby/buildkit:v0.33.1
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

