published 5 Oct 2026 · updated 13 Nov 2026
Crafted Git build source can bypass certain policy validation
6.0MediumCVSS 6.0EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Moby | <=0.33.0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket