Skip to main content
VulnerabilityPublished

CVE-2026-93326: moby BuildKit · Incorrect Behavior Order: Validate Before Canonicalize

Affects moby BuildKitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
mobyBuildKitAffected
  • <=0.33.0
Fixed in–
GitHubgithub.com/moby/buildkitpkg:github/github.com/moby/buildkitOther threatsAffected
  • <=0.33.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should ensure that stricter validations such as commit SHA, commit data, or signature verification are enforced as these remain effective against this issue.

Description

CVE-2026-93326 is a medium severity vulnerability in moby BuildKit affecting versions from 0 up to and including 0.33.0. It involves incorrect behavior order where validation occurs before canonicalization in a Git source build step. This flaw allows a malicious build definition to make a Git repository appear as if it originates from a different remote URL during cloning. However, stricter validations based on commit SHA, commit data, or signatures remain effective.

References

Community reviews

Loading reviews…