BuildKit: Incorrect Behavior Order: Validate Before Canonicalize (CVE-2026-93326)

What is affected, what to do

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.

Update BuildKit to version 0.33.1.

Affected

• Moby BuildKit lte *..0.33.0

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2

NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

Read in glossary

Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.

CRA

The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

Read in glossary

From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.

ISO/IEC 27001

ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

Read in glossary

Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

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.

Source: BSI WID Portal

Vendors and products

• Moby BuildKit
• Open Source Buildkit

Weakness classes (CWE)

• CWE-180Incorrect Behavior Order: Validate Before Canonicalize

  Variant

  The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.

  Entry at MITRE CWE-180

References & sources

• github.commoby/buildkit/security/advisories/GHSA-4hgw-qrhw-fhg8Vendor advisory
• github.commoby/buildkit/releases/tag/v0.33.1Patch
• github.commoby/buildkit/security/advisories/GHSA-p3rc-w3hc-pqvvVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-f2v9-hprr-32q3Vendor advisory
• github.commoby/buildkit/security/advisories/GHSA-mgqf-486f-49vpVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-2f5p-x9ph-g97xVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-r456-g3gm-cvxfVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-fjj4-h6vf-m9hjVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-66hf-6vf5-87hcVendor advisory
• github.commoby/buildkit/security/advisories/GHSA-9728-qjrv-2xh2Vendor advisory
• github.commoby/buildkit/security/advisories/GHSA-cv6p-7w7g-xjwqVendor advisory

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

1. 06.10.2026Record modifiedCISA ADP

   CISA assessment (SSVC): exploitation: none known, automatable: no

   Show the original change

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   SSVC assessment	added	—	{"id":"CVE-2026-93326","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-06T13:48:15.390037Z"}

   Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

2. 05.10.2026Receiveddocker.com

   CVSS V4.0: AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

   Weakness type: CWE-180

   Description added or changed

   New references:

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

   Individual changes of this event as published by NVD

   Type	Action	Before	After
   Description	added	—	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.
   CVSS	added	—	AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
   Weakness type (CWE)	added	—	CWE-180
   Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/93xxx/CVE-2026-93326.json">CVE-2026-93326</a>
   Reference	added	—	https://github.com/moby/buildkit/releases/tag/v0.33.1
   Reference	added	—	https://github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hc

   Source identifier: security@docker.com