CVE-2026-93326

Crafted Git build source can bypass certain policy validation

MEDIUM
6
CVSS Score
Published: October 5, 2026 at 08:13 PM UTC
Updated: October 6, 2026 at 03:08 PM UTC
1 product affected across 1 vendorBuildKit

Using BuildKit by moby?

Get instant alerts when new vulnerabilities affect BuildKit - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 0.33.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6MEDIUMDocker
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-180

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card