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.
Metrics
Affected Vendors & Products
References
History
Tue, 06 Oct 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 05 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Moby
Moby buildkit |
|
| Vendors & Products |
Moby
Moby buildkit |
Mon, 05 Oct 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Crafted Git build source can bypass certain policy validation | |
| Weaknesses | CWE-180 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: Docker
Published: 2026-10-05T20:13:27.383Z
Updated: 2026-10-06T13:48:34.715Z
Reserved: 2026-09-17T17:18:44.985Z
Link: CVE-2026-93326
Updated: 2026-10-06T13:48:20.721Z
Status : Awaiting Analysis
Published: 2026-10-05T21:16:37.907
Modified: 2026-10-06T15:08:38.397
Link: CVE-2026-93326
No data.