CVE-2026-93319: moby BuildKit · Unsynchronized Access to Shared Data in a Multi-threaded Context
Affects moby BuildKitSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium.
Data as of 19 Nov 2026, 20:26 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mobyBuildKit | Affected
| Fixed in– |
GitHubgithub.com/moby/buildkitpkg:github/github.com/moby/buildkitOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor vendor communications for updates and consider restricting access to the internal API to trusted frontends only.
Description
CVE-2026-93319 is a medium severity vulnerability in moby BuildKit versions up to 0.33.0. It involves unsynchronized access to shared data in a multi-threaded context, where a malicious external BuildKit frontend can send internal API requests that may cause a data race leading to a daemon panic.