CVE-2026-93316 Starting daemon with --cdi-disabled flag can lead to panic on specific builds

High 7.1 Published Updated

Attackers can crash the BuildKit daemon by triggering a null pointer dereference when using CDI devices with the --cdi-disabled flag.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-93316?

CVE-2026-93316 is a high-severity vulnerability in moby BuildKit, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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.

Weakness: CWE-476

Which versions are affected by CVE-2026-93316?

How do I fix CVE-2026-93316?

No fix has been published for CVE-2026-93316 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-93316 being exploited?

There is no known exploitation of CVE-2026-93316 in the wild and no public exploit code.

Sources

Also known as GHSA-r456-g3gm-cvxf, UBUNTU-CVE-2026-93316.

Is CVE-2026-93316 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free