CVE-2026-93326Network attack vectorHinoki check available

Git source-policy bypass via mismatched repository identity

Published Oct 5, 2026 · Updated Oct 5, 2026

Source-policy bypass in Moby Project BuildKit 0.33.0 and earlier allows remote authenticated users to clone a disallowed Git repository. A crafted Git source can supply a bundle locator or full remote URL that differs from the source identifier evaluated by URL-based policy rules, so the repository cloned is not the one those rules checked. Exploitation requires an accepted build definition and optional Git-source policies based on repository URLs; commit, metadata, and signature checks still apply.

CVSS severity6.0
Medium
EPSS probability0.25%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Source-policy bypass in Moby Project BuildKit 0.33.0 and earlier allows remote authenticated users to clone a disallowed Git repository. A crafted Git source can supply a bundle locator or full remote URL that differs from the source identifier evaluated by URL-based policy rules, so the repository cloned is not the one those rules checked. Exploitation requires an accepted build definition and optional Git-source policies based on repository URLs; commit, metadata, and signature checks still apply.

The record

CVE
CVE-2026-93326
Published
Oct 5, 2026
Updated
Oct 5, 2026
Vendor
Moby Project
Product
BuildKit
Classifications
CWE-180, T1195.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 5, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=0.33.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Moby Project · BuildKitversion=0 <=0.33.0

Published CVSS scores

6.0Moby ProjectCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-180Incorrect Behavior Order: Validate Before Canonicalize
T1195.001Compromise Software Dependencies

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started