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

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

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-r456-g3gm-cvxf, UBUNTU-CVE-2026-93316

## 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 (NULL Pointer Dereference)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93316 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-93316 in the wild and no public exploit code.

Affected product: moby BuildKit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93316/ (Markdown: https://insights.sbomify.com/CVE-2026-93316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93316
- OSV: https://osv.dev/vulnerability/CVE-2026-93316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93316/
Summaries are generated and may contain mistakes; the official description above is the record.