CVE-2026-93316

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

Published Oct 5, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Remediation

Vendor Workaround

The issue only appears when --cdi-disabled is set as a specific flag in daemon startup or TOML config. Without it, builds get regular entitlement checks and fail cleanly if the user doesn't allow specific CDI entitlements per build.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-248
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Moby
Moby buildkit
Vendors & Products Moby
Moby buildkit
Type Values Removed Values Added
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.
Title Starting daemon with --cdi-disabled flag can lead to panic on specific builds
Weaknesses CWE-476
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Docker
Published
Updated
Oct 5, 2026, 7:05 PM
Reserved
Sep 17, 2026, 5:17 PM
Status
Awaiting Analysis
Published
Oct 5, 2026, 6:17 PM
Modified
Oct 6, 2026, 3:08 PM
Severity
Moderate
Public date
Oct 5, 2026, 5:42 PM