CVE-2026-93316

Starting daemon with --cdi-disabled flag can lead to panic on specific builds

HIGH
7.1
CVSS Score
Published: October 5, 2026 at 05:42 PM UTC
Updated: October 6, 2026 at 03:08 PM UTC
1 product affected across 1 vendorBuildKit

Using BuildKit by moby?

Get instant alerts when new vulnerabilities affect BuildKit - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.33.1

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHDocker
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card