CVE-2026-93326
Published: October 9, 2026Last modified: October 20, 2026
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.
Status
| Product | Release | Package | Status |
|---|---|---|---|
| Alpaquita Linux | 23 LTS | buildah | Not affected (1.28.0-r1) |
| docker | Not affected (20.10.21-r1) | ||
| podman | Not affected (4.3.1-r0) | ||
| 25 LTS | buildah | Not affected (1.40.0-r0) | |
| docker | Vulnerable (28.2.1-r0) | ||
| docker-cli-buildx | Not affected (0.24.0-r0) | ||
| osv-scanner | Not affected (2.1.0-r4) | ||
| podman | Not affected (5.5.0-r0) | ||
| Stream | buildah | Not affected (1.31.0-r0) | |
| docker | Fixed (29.9.0-r0) | ||
| docker-cli-buildx | Not affected (0.11.0-r0) | ||
| osv-scanner | Not affected (2.1.0-r2) | ||
| podman | Not affected (4.5.1-r1) |