CVE-2026-93326
Crafted Git build source can bypass certain policy validation
No known exploitation. EPSS puts it in the 15th percentile. Only a workaround so far.
What to do
No fixed build is published yet. The vendor describes a workaround.
- moby BuildKitAffected: ≤ 0.33.0Upgrade to: after 0.33.0Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 15th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 1 day, from the signal feeds we watch.
- Workaround availablerecord updated
- Workaround availablepublished, weakness classified, record updated
Affected products
Technical detail
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for BuildKit, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI