CVE-2026-93316: Starting daemon with --cdi-disabled flag can lead to panic on specific builds
High · CVSS 7.1 (CVSS 4.0)EPSS 0.23%, 14th percentilePublished Updated Assigner: Docker
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.
CWE-476
Tracked companies
Mapped from the CVE’s affected-product data, NVD CPE matches, vendor advisories or package feeds. A mapping means the vendor’s software is named, not that its hosted service was exposed.
Status incidents that name it
No tracked status incident names this CVE.
Affected vendors and products
moby: BuildKit
References
- CVE record on cve.org (opens in new tab)
- NVD entry (opens in new tab)
- github.com/moby/buildkit/releases/tag/v0.33.1 (opens in new tab)
- github.com/moby/buildkit/security/advisories/GHSA-r456-g3gm-cvxf (opens in new tab)
- CVE records from the CVE Program (cve.org). CVE® is a registered trademark of The MITRE Corporation. (opens in new tab)
- This product uses data from the NVD API but is not endorsed or certified by the NVD. (opens in new tab)
- Known Exploited Vulnerabilities catalog from CISA. (opens in new tab)
- EPSS scores from FIRST (Exploit Prediction Scoring System). (opens in new tab)