Advisory severityHigh7.1Docker

High [CVE-2026-93316] If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices

This high-severity Docker advisory covers CVE-2026-93316 affecting BuildKit.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-93316 Source published Oct 5, 2026Source updated Oct 6, 2026

VulniPulse record published Oct 5, 2026Record updated Oct 6, 2026

CVE-2026-93316

Affected products & platforms

DockerBuildKit / Compose

Open source advisory

Android app · Google Play

Monitor future Docker CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

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 versions

BuildKit before 0.33.1

NVD record · high-confidence parse· fetched 4 days ago·verify at source

Fixed versions

0.33.1

NVD record · high-confidence parse· fetched 4 days ago·verify at source

Mitigation

Upgrade to a fixed release: 0.33.1. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

NVD record · high-confidence parse· fetched 4 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.