Vulnerability · Published Oct 5, 2026 · Assigned by Docker
CVE-2026-93316Starting daemon with --cdi-disabled flag can lead to panic on specific builds
High 7.1
In plain English
A high-severity null pointer dereference in BuildKit from moby. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 14% of all known vulnerabilities).
Severity (CVSS 4.0)7.1High
Exploit odds (30 days)0.2%top 85.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu:26.04:LTS | docker.io | no fix listed | UBUNTU-CVE-2026-93316 |
| Ubuntu:26.10 | docker.io | no fix listed | UBUNTU-CVE-2026-93316 |
| Ubuntu:26.04:LTS | docker.io-app | no fix listed | UBUNTU-CVE-2026-93316 |
| Ubuntu:26.10 | docker.io-app | no fix listed | UBUNTU-CVE-2026-93316 |
Affected products (as reported)
Weakness: CWE-476 · 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