CVE-2026-93318

published 5 Oct 2026 · updated 13 Nov 2026

Cache poisoning via unvalidated image layer DiffIDs

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.33.1.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Moby<0.33.10.33.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93318 severity on Zeptric[![CVE-2026-93318](https://zeptric.io/badge/cve/CVE-2026-93318.svg)](https://zeptric.io/cve/CVE-2026-93318)