PoC Monitor
← All CVEs
CVE-2026-93318published 5 Oct 2026 17:45 UTCData: JSON · API

Moby BuildKit

Cache poisoning via unvalidated image layer DiffIDs

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-354
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

moby BuildKit
  • < 0.33.1

Fixed in 0.33.1

Mitigation

Upgrade BuildKit to 0.33.1 or later.

Workaround

Do not share BuildKit daemon cache between trusted and untrusted builds. Use isolated BuildKit daemons or ephemeral builders for untrusted image sources, or prune BuildKit cache after processing untrusted images. Disabling stargz alone is not sufficient because regular snapshotters are also affected.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published5 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.