Quick answers
- Is CVE-2026-93326 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93326 being exploited in the wild.
- How severe is CVE-2026-93326?
- Informational severity, published 5 October 2026.
- Which products and versions are affected?
- Moby BuildKit <= v0.33.0.
- Is there a fix for CVE-2026-93326?
- Yes: fixed in v0.33.1+. Until then: Issue only affects builds with optional Build policies that include specific Git source URL validation rules. If not using Git source policy rules, the vulnerability does not apply. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93326 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-93326?
- Check whether you run Moby BuildKit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: v0.33.1+
Issue only affects builds with optional Build policies that include specific Git source URL validation rules. If not using Git source policy rules, the vulnerability does not apply.
Technical details
A malicious Git build source definition can be crafted to bypass BuildKit's source policy validation rules that match on repository URL. The vulnerability allows an attacker to spoof the remote URL seen during Git clone operations. However, stricter validation policies based on commit SHA, commit data, or signatures are not affected and continue to function correctly.
Affected products
- Moby BuildKit <= v0.33.0
Timeline
- 2026-09-30: disclosed
- 2026-09-30: patched