CVE-2026-93326: Crafted Git build source can bypass certain policy validation
Medium · CVSS 6.0 (CVSS 4.0)EPSS 0.25%, 16th percentilePublished Updated Assigner: Docker
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.
CWE-180
Tracked companies
Mapped from the CVE’s affected-product data, NVD CPE matches, vendor advisories or package feeds. A mapping means the vendor’s software is named, not that its hosted service was exposed.
Status incidents that name it
No tracked status incident names this CVE.
Affected vendors and products
moby: BuildKit
References
- CVE record on cve.org (opens in new tab)
- NVD entry (opens in new tab)
- github.com/moby/buildkit/releases/tag/v0.33.1 (opens in new tab)
- github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hc (opens in new tab)
- CVE records from the CVE Program (cve.org). CVE® is a registered trademark of The MITRE Corporation. (opens in new tab)
- This product uses data from the NVD API but is not endorsed or certified by the NVD. (opens in new tab)
- Known Exploited Vulnerabilities catalog from CISA. (opens in new tab)
- EPSS scores from FIRST (Exploit Prediction Scoring System). (opens in new tab)