Cache poisoning via unvalidated image layer DiffIDs
Published Oct 5, 2026 · Updated Oct 5, 2026
Cache poisoning in Moby Project BuildKit 0.33.0 and earlier allows remote attackers to run code in later builds via crafted images. The daemon derives image-source cache and snapshot identity from advertised layer DiffIDs without checking them against the applied layer contents. Exploitation requires a shared or persistent cache to process the malicious image before a victim build; substituted code can read build secrets, alter artifacts, or hang that build.
Summary
What happened
Cache poisoning in Moby Project BuildKit 0.33.0 and earlier allows remote attackers to run code in later builds via crafted images. The daemon derives image-source cache and snapshot identity from advertised layer DiffIDs without checking them against the applied layer contents. Exploitation requires a shared or persistent cache to process the malicious image before a victim build; substituted code can read build secrets, alter artifacts, or hang that build.
The record
- CVE
- CVE-2026-93318
- Published
- Oct 5, 2026
- Updated
- Oct 5, 2026
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-354
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 5, 2026CVE publishedPublication date reported by the CVE source.
- Oct 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.33.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started