BuildKit panics on CDI device builds if started with --cdi-disabled
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-476.
Summary
moby BuildKit from 0 before 0.33.1 is affected. A NULL pointer dereference (CWE-476) makes the daemon panic when builds try to use CDI devices after it was started with --cdi-disabled. A low-privileged user on the network can crash the daemon, and this can also happen by accident.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| moby | BuildKit | before 0.33.1 | 0.33.1 | Patch available | CNA |
- BuildKit Vendormoby Affected before 0.33.1 Fixed in 0.33.1 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:mobyproject:buildkit:*:*:*:*:*:*:*:* | — | — | Mobyproject |
- cpe:2.3:a:mobyproject:buildkit:*:*:*:*:*:*:*:* Versions — — ·Mobyproject
Remediation
Update moby BuildKit to version 0.33.1 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA BuildKit (moby) Fixed in 0.33.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
moby BuildKit 0.33.1
4 records Highest priority Priority LOW 4 LOW
Other records, highest priority first
- TI-2026-67814 Cache poisoning in BuildKit via unvalidated image layer DiffIDsPriority LOW 34
- TI-2026-67813 Container blob cache can accept unverified content in BuildKitPriority LOW 26
- TI-2026-68038 Race condition in BuildKit CA cleanup lets build steps disrupt itPriority LOW 25
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
Not affected: 2 products
- Red Hat Hardened Images
- Red Hat Quay 3
Timeline
- 2026-10-05 Threatist record created from CVE-2026-93316
- 2026-10-05 CISA SSVC decision points changed
- 2026-10-05 Priority changed: MEDIUM → LOW
- 2026-10-06 Affected versions changed · Red Hat
- 2026-10-06 CVSS score added · Red Hat
- 2026-10-07 Affected versions changed · Red Hat
- 2026-10-20 Affected versions changed · Red Hat
- 2026-10-21 Affected versions changed · Red Hat
References
More moby vulnerabilities
- TI-2026-14229 Tar extraction in moby/go-archive can write outside the destination directory via link following CVSS 4.0HIGH 7.1
- TI-2021-12512 Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx CVSS 3.1HIGH 7.1
- TI-2024-27462 Moby authz zero length regression CVSS 3.1CRITICAL 10.0
- TI-2024-15672 BuildKit interactive containers API does not validate entitlements check CVSS 3.1CRITICAL 9.8
- TI-2024-15671 BuildKit possible host system access from mount stub cleaner CVSS 3.1CRITICAL 10.0
- TI-2026-26365 Moby: AuthZ plugin bypass with oversized request body CVSS 3.1HIGH 8.8
Sources
- CVE-2026-93316 · CVE Program
- CVE-2026-93316 · NVD
- FIRST EPSS
- CVE-2026-93316 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences