# CVE-2026-93320: BuildKit improperly handles special files in build snapshots

> Attackers can trick BuildKit into accessing host devices or blocking operations via special file inodes, requiring a patch.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** AZL-106806, GHSA-9728-qjrv-2xh2, UBUNTU-CVE-2026-93320

## What is CVE-2026-93320?

CVE-2026-93320 is a medium-severity path traversal vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow unintended host device access.

Weakness: CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-93320?


## How do I fix CVE-2026-93320?

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

## Is CVE-2026-93320 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93320 is a medium-severity path traversal vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93320 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-93320/ (Markdown: https://insights.sbomify.com/CVE-2026-93320/index.md)
```

## Sources

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

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