High severity · published Oct 5, 2026
CVE-2026-93316
Starting daemon with --cdi-disabled flag can lead to panic on specific builds
7.1
CVSS
0.2%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 14% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
BU
BuildKit · moby
before 0.33.1 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93316
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-93316
vendor-advisory
https://github.com/moby/buildkit/security/advisories/GHSA-r456-g3gm-cvxf
patch
https://github.com/moby/buildkit/releases/tag/v0.33.1
More from BuildKit
9.8
CVE-2026-33747
BuildKit vulnerable to malicious frontend causing file escape outside of storage root
7.5
CVE-2026-93318
Cache poisoning via unvalidated image layer DiffIDs
7.5
CVE-2026-15793
Git source checkout from a bundle file could lead to command injection
7.5
CVE-2026-15792
Possible panic when incorrect parameters sent from frontend
7.5
CVE-2026-15791
LLB file operation can be tricked to remove /tmp directory contents