Skip to main content
VulnerabilityPublished

CVE-2026-93318: moby BuildKit · Improper Validation of Integrity Check Value

Affects moby BuildKitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.33.1 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.33.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/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 20 Nov 2026.

What to do

Upgrade BuildKit and github.com/moby/buildkit to 0.33.1.

Affected software

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

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

Description

A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents. If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access other build resources, alter output artifacts, or hang the build. The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz.

References

Community reviews

Loading reviews…