CVE-2026-93318
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 6% of all known CVEs.
References
Related Vulnerabilities
Other CWE-354 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-48795 | Medium | 5.9 | 94% | - | Fix |
| CVE-2019-1166 | Medium | 5.9 | 68% | - | - |
| CVE-2024-3596 | Critical | 9.0 | 15% | - | Fix |
| CVE-2020-26141 | Medium | 6.5 | 3.1% | - | Fix |
| CVE-2020-25862 | High | 7.5 | 2.4% | - | Fix |
| CVE-2023-38802 | High | 7.5 | 1.8% | - | Fix |
Common questions
How do I fix CVE-2026-93318?
No published fix for CVE-2026-93318 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-93318 being actively exploited?
Not that we know of. CVE-2026-93318 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.17% is the estimated probability that it will be exploited in the next 30 days. That is higher than 6% of all scored CVEs.
How severe is CVE-2026-93318?
CVE-2026-93318 has a CVSS v4 base score of 7.5, rated important. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-93318
Markdown
[](https://tridentstack.com/cve/CVE-2026-93318)HTML
<a href="https://tridentstack.com/cve/CVE-2026-93318"><img src="https://tridentstack.com/cve/badge/CVE-2026-93318.svg" alt="CVE-2026-93318"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-06.