Quick answers
- Is CVE-2026-93319 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93319 being exploited in the wild.
- How severe is CVE-2026-93319?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Moby BuildKit <=v0.33.0.
- Is there a fix for CVE-2026-93319?
- Yes: fixed in v0.33.1. Until then: Avoid using external BuildKit frontends from untrusted sources. Dockerfile builds are unaffected by this vulnerability.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-09-30"}, {"kind": "patched", "at": "2026-09-30"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93319 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-93319?
- 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 using external BuildKit frontends from untrusted sources. Dockerfile builds are unaffected by this vulnerability.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-09-30"}, {"kind": "patched", "at": "2026-09-30"}]
Technical details
A data race in the BuildKit daemon's internal API request handling allows a malicious external frontend to send specially crafted requests that trigger a concurrent access condition, causing a daemon panic. The vulnerability affects BuildKit versions up to v0.33.0 and requires the use of an untrusted external frontend; Dockerfile builds are not affected. The fix is available in v0.33.1 and later.
Affected products
- Moby BuildKit <=v0.33.0