Skip to main content
Vulnerability Database/CVE-2026-93316

CVE-2026-93316: BuildKit Daemon DOS Vulnerability

CVE-2026-93316 is a denial of service flaw in BuildKit daemon that causes panic when CDI devices are used with --cdi-disabled flag. This post explains its impact, affected versions, and mitigation steps.

Published:

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-93316 Overview

CVE-2026-93316 is a null pointer dereference vulnerability [CWE-476] in the Moby BuildKit daemon. When the daemon runs with the --cdi-disabled flag, builds that request Container Device Interface (CDI) devices trigger a daemon panic. The crash can be induced accidentally by a legitimate build or deliberately by an attacker with build submission privileges. The result is a denial-of-service condition that terminates the BuildKit daemon process and interrupts all in-flight builds. Upstream maintainers addressed the issue in BuildKit v0.33.1.

Critical Impact

An authenticated user who can submit builds to a BuildKit daemon started with --cdi-disabled can crash the daemon by referencing a CDI device, disrupting continuous integration pipelines and shared build infrastructure.

Affected Products

  • Moby BuildKit daemon versions prior to v0.33.1 when started with the --cdi-disabled flag
  • Container build pipelines and CI/CD systems embedding vulnerable BuildKit releases
  • Downstream distributions that package BuildKit as a build backend

Discovery Timeline

  • 2026-10-05 - CVE-2026-93316 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-93316

Vulnerability Analysis

The flaw resides in how the BuildKit daemon handles CDI device requests when CDI support is explicitly disabled at startup. The Container Device Interface is a specification for exposing devices such as GPUs and accelerators to containerized workloads. Operators disable CDI with --cdi-disabled when they do not want builds to access host devices.

Instead of rejecting CDI device requests with a controlled error, the daemon code path dereferences an uninitialized or nil CDI registry structure. This triggers a runtime panic that terminates the entire daemon process. All concurrent builds fail, and queued jobs are lost until the daemon is restarted.

Root Cause

The root cause is a missing guard around the CDI resolver when the subsystem has not been initialized. With --cdi-disabled, the CDI manager is never populated, yet the request handler still invokes methods on it when a build references a CDI device. This produces a null pointer dereference consistent with [CWE-476].

Attack Vector

Exploitation requires network-reachable access to the BuildKit daemon API and the privilege to submit a build definition. An attacker crafts a Dockerfile or LLB (low-level build) request that specifies a CDI device, for example by including a --device directive that references a CDI-qualified name. When the daemon processes the request, it panics and exits. The vector is network-based and requires low privileges with no user interaction, aligning with the attack scope of shared build infrastructure.

No verified exploit code is published. See the GitHub Security Advisory GHSA-r456-g3gm-cvxf for technical details.

Detection Methods for CVE-2026-93316

Indicators of Compromise

  • Unexpected termination of the buildkitd process accompanied by Go runtime panic traces referencing CDI code paths.
  • Build jobs failing with connection reset or EOF errors immediately after submitting a workload that specifies a CDI device.
  • Repeated daemon restarts correlated with build requests from the same client or namespace.

Detection Strategies

  • Inspect buildkitd logs for runtime error: invalid memory address or nil pointer dereference entries emitted during build request handling.
  • Audit build submissions for Dockerfiles or LLB payloads that request CDI devices on daemons started with --cdi-disabled.
  • Correlate CI/CD pipeline failures with daemon crash events to identify repeatable triggers.

Monitoring Recommendations

  • Alert on buildkitd process exits and systemd service restarts on build hosts.
  • Track BuildKit daemon version inventory and flag any hosts running versions earlier than v0.33.1.
  • Monitor build API error rates and sudden drops in build throughput that may indicate crash loops.

How to Mitigate CVE-2026-93316

Immediate Actions Required

  • Upgrade BuildKit to v0.33.1 or later on all build hosts and CI runners.
  • Restrict access to the BuildKit daemon socket and gRPC endpoint to trusted users and pipelines only.
  • Review existing builds for CDI device references and reconcile them with the daemon configuration.

Patch Information

The fix is included in BuildKit release v0.33.1. The upstream advisory is published as GHSA-r456-g3gm-cvxf. Operators running container platforms that embed BuildKit should apply vendor-provided updates once they incorporate the patched release.

Workarounds

  • If upgrading immediately is not feasible, remove the --cdi-disabled flag and leave CDI enabled with no devices configured, so requests resolve through the initialized registry.
  • Enforce admission controls that reject build definitions containing CDI device directives on affected daemons.
  • Isolate BuildKit daemons behind authenticated proxies to limit who can submit builds.
bash
# Verify installed BuildKit version and upgrade if below v0.33.1
buildkitd --version

# Example systemd override removing --cdi-disabled as an interim workaround
# /etc/systemd/system/buildkit.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/local/bin/buildkitd --addr unix:///run/buildkit/buildkitd.sock

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.