CVE-2026-93326Crafted Git build source can bypass certain policy validation
Updated under an hour ago ()
Does this affect you?
It affects moby BuildKit. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 6.0 MEDIUM (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
- Weakness (CWE)
- CWE-180
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Docker
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 6, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
moby BuildKit moby:buildkit (from the name) | through 0.33.0 | CNA record |
References
- https://github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hcvendor-advisory
- https://github.com/moby/buildkit/releases/tag/v0.33.1patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.