Back to CVE records
High 7.1Published Oct 5, 2026
CVE-2026-93316Starting daemon with --cdi-disabled flag can lead to panic on specific builds
Updated under an hour ago ()
Does this affect you?
It affects moby BuildKit. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.24%, higher than 13% of scored CVEs.
Do this next
Start free and add your stack
Free account, 1 product
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.
- CVSS
- 7.1 HIGH (v4.0, CNA)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
- Weakness (CWE)
- CWE-476
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.24% (percentile 13)
- Assigned by
- Docker
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 5, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
moby BuildKit moby:buildkit (from the name) | before 0.33.1 | CNA record |
References
- https://github.com/moby/buildkit/security/advisories/GHSA-r456-g3gm-cvxfvendor-advisory
- https://github.com/moby/buildkit/releases/tag/v0.33.1patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.