Skip to main content

CVE-2026-93326: CWE-180: Incorrect Behavior Order: Validate Before Canonicalize in moby BuildKit

0
Medium
VulnerabilityCVE-2026-93326cvecve-2026-93326cwe-180
Published: 10/05/2026 (10/05/2026, 20:13:27 UTC)
Source: CVE Database V5
Vendor/Project: moby
Product: BuildKit

Description

CVE-2026-93326 is a medium severity vulnerability in moby BuildKit where a specially crafted Git build step can bypass some policy validation rules by making the repository appear to come from a different remote URL during Git clone. However, stricter validations based on commit SHA, commit data, or signatures remain effective.

CVSS v4.0

Score 6.0medium

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
Low
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

moby

BuildKit

Affected versions
>=0 <=0.33.0
GitHub Actionsmore threats →cve
github.com/moby/buildkit
pkg:github/github.com/moby/buildkit
Affected versions
>=0 <=0.33.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/05/2026, 20:33:48 UTC

Technical Analysis

This vulnerability involves an incorrect behavior order (CWE-180) in moby BuildKit's handling of Git source build steps. A malicious build definition can manipulate the repository URL seen during Git clone, potentially bypassing some policy validation rules that rely on the repository URL. Despite this, validations that depend on commit SHA, commit data, or signatures are still correctly enforced, limiting the scope of the bypass.

Potential Impact

An attacker can craft a build step to make the repository appear as if it originates from a different remote URL, potentially bypassing URL-based policy validations. However, since commit SHA, commit data, and signature validations are still applied correctly, the impact is limited to scenarios relying solely on URL validation. There is no indication of remote code execution or data compromise solely from this vulnerability.

Mitigation Recommendations

No official patch or fix is currently documented. Users should rely on stricter validation policies that include commit SHA, commit data, or signature checks, as these are not bypassed by this vulnerability. Monitor vendor advisories for updates or patches addressing this issue.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Docker
Date Reserved
2026-09-17T17:18:44.985Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6ac4063a2cdf04f65634e08d

Added to database: 10/05/2026, 20:19:06 UTC

Last enriched: 10/05/2026, 20:33:48 UTC

Last updated: 10/05/2026, 20:34:04 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses