# CVE-2026-93326: Crafted Git build source can bypass certain policy validation

> Attackers can bypass policy validation in BuildKit by crafting Git build sources to spoof remote URLs, undermining security controls.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** AZL-106812, BELL-CVE-2026-93326, GHSA-66hf-6vf5-87hc, UBUNTU-CVE-2026-93326

## What is CVE-2026-93326?

CVE-2026-93326 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-93326?


## How do I fix CVE-2026-93326?

Apply the vendor's patch.

## Is CVE-2026-93326 being exploited?

There is no known exploitation of CVE-2026-93326 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93326 and fix it if it is affected.

What it is: CVE-2026-93326 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93326 in the wild and no public exploit code.

Affected product: moby BuildKit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93326/ (Markdown: https://insights.sbomify.com/CVE-2026-93326/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93326
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93326
- OSV: https://osv.dev/vulnerability/CVE-2026-93326

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93326/
Summaries are generated and may contain mistakes; the official description above is the record.