CVE-2026-93316

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 5, 2026

Last Modified

October 6, 2026

Advisory Details (2)

Auto-updated Oct 5, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Starting daemon with --cdi-disabled flag can lead to panic on specific builds · Advisory · moby/buildkit · GitHub

Affected: v0.32.3+

https://github.com/moby/buildkit/security/advisories/GHSA-r456-g3gm-cvxf
GitHub release Patch Available

v0.33.1

Patch available: moby/buildkit v0.33.1

https://github.com/moby/buildkit/releases/tag/v0.33.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-13 04:27 UTCEG score recompute
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-12 14:43 UTCEG score recompute
  5. 2026-10-11 19:12 UTCEG score recompute
  6. 2026-10-11 16:28 UTCEG score recompute
  7. 2026-10-11 15:48 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-11 13:42 UTCEG score recompute
  10. 2026-10-11 03:50 UTCEG score recompute
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-10 03:53 UTCEG score recompute
  13. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-09 03:57 UTCEG score recompute
  15. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-08 04:01 UTCEG score recompute
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-06 15:33 UTCEG score recompute
  19. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-05 20:26 UTCEG score recompute
  21. 2026-10-05 19:22 UTCEG score recompute
  22. 2026-10-05 18:23 UTCEG score recompute
  23. 2026-10-05 17:46 UTCEG score recomputeFirst assessed: 7.1 HIGH
  24. 2026-10-05 17:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-93316?
CVE-2026-93316 is a high-severity vulnerability; its CVE record was published on October 5, 2026. If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices. This can happen maliciously or by accident.
When was the CVE record for CVE-2026-93316 published?
The CVE record for CVE-2026-93316 was published on October 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-93316 actively exploited?
CVE-2026-93316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93316?
CVE-2026-93316 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93316?
A fix for CVE-2026-93316 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93316

Explore →

Is Your Infrastructure Affected by CVE-2026-93316?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs