Medium severity · published Oct 5, 2026
CVE-2026-93326
Crafted Git build source can bypass certain policy validation
6.0
CVSS
0.2%
EPSS
No
On KEV
Description
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 16% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
BU
BuildKit · moby
through 0.33.0 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93326
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-93326
vendor-advisory
https://github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hc
patch
https://github.com/moby/buildkit/releases/tag/v0.33.1
More from BuildKit
9.8
CVE-2026-33747
BuildKit vulnerable to malicious frontend causing file escape outside of storage root
7.5
CVE-2026-93318
Cache poisoning via unvalidated image layer DiffIDs
7.5
CVE-2026-15793
Git source checkout from a bundle file could lead to command injection
7.5
CVE-2026-15792
Possible panic when incorrect parameters sent from frontend
7.5
CVE-2026-15791
LLB file operation can be tricked to remove /tmp directory contents
