Quick answers
- Is CVE-2026-93320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93320 being exploited in the wild.
- How severe is CVE-2026-93320?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Moby BuildKit <=v0.33.0.
- Is there a fix for CVE-2026-93320?
- Yes: fixed in v0.33.1. Until then: Avoid running untrusted builds. For rootful worker deployments, consider switching to rootless mode to mitigate device access, though this does not prevent denial-of-service attacks from special files. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93320 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-93320?
- Check whether you run Moby BuildKit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: v0.33.1
Avoid running untrusted builds. For rootful worker deployments, consider switching to rootless mode to mitigate device access, though this does not prevent denial-of-service attacks from special files.
Technical details
BuildKit improperly validates file types when performing file operations in build snapshots, allowing special file inodes to be used where regular files are expected. The vulnerability affects snapshot reads and LLB mkfile operations. Local attack vector with user interaction required; on rootful workers, this permits unintended host device access; rootless workers are protected from device access but remain vulnerable to operations being blocked.
Affected products
- Moby BuildKit <=v0.33.0
Timeline
- 2026-09-30: disclosed
- 2026-09-30: patched