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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| moby | BuildKit | ≤ 0.33.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | docker.io +1 | No fix yet | — |
| Ubuntu 26.04 LTS | docker.io +1 | No fix yet | — |
Show 5 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 24.04 LTS | docker.io +1 | No fix yet | — |
| Ubuntu Pro 22.04 LTS | docker.io +1 | No fix yet | — |
| Ubuntu Pro 20.04 LTS | docker.io +1 | No fix yet | — |
| Ubuntu Pro 18.04 LTS | docker.io | No fix yet | — |
| Ubuntu Pro 16.04 LTS | docker.io | No fix yet | — |
Azure Linux
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Azure Linux 3 | moby-engine | No fix yet | — |
Advisories 1
- WID-SEC-2026-3741 BuildKit: Mehrere Schwachstellen BSI CERT-Bund (WID) · Oct 25, 2026