CVE-2026-93318: CWE-354: Improper Validation of Integrity Check Value in moby BuildKit
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.
CVSS v4.0
Score 7.5high
Affected software
moby
BuildKit
pkg:github/github.com/moby/buildkitRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because BuildKit uses advertised DiffIDs to derive cache and snapshot identity without verifying that these DiffIDs match the actual layer contents. If a BuildKit daemon with shared or persistent cache processes a malicious image exploiting this flaw, a later build using the victim image may mount attacker-controlled layer contents as the base image. This can lead to execution of attacker-controlled code within the build environment, including replacing commonly executed paths such as /bin/sh. Both regular and lazy-pulling snapshotters like stargz are affected. The CVSS 4.0 score is 7.5, indicating high severity.
Potential Impact
An attacker can cause BuildKit to use malicious layer contents during a build, potentially executing arbitrary code in the build environment. This can lead to unauthorized access to build secrets, manipulation of build resources, alteration of output artifacts, or denial of service by hanging the build process. The vulnerability affects the integrity of the build process and can compromise the security of container images built with affected versions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using shared or persistent caches with untrusted images and consider isolating build environments to reduce risk. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Docker
- Date Reserved
- 2026-09-17T17:17:49.216Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ac3e69d2cdf04f65628b487
Added to database: 10/05/2026, 18:04:13 UTC
Last enriched: 10/05/2026, 18:18:29 UTC
Last updated: 10/05/2026, 19:34:03 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.