CVE-2026-93319

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100CISA SSVC

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
Severity57% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 5, 2026

Last Modified

October 6, 2026

Advisory Details (2)

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

A malicious frontend can cause a daemon panic · Advisory · moby/buildkit · GitHub

Affected: v0.33.1+

https://github.com/moby/buildkit/security/advisories/GHSA-4hgw-qrhw-fhg8
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 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-10 08:13 UTCEG score recompute
  2. 2026-10-09 20:08 UTCEPSS rescore
  3. 2026-10-09 10:03 UTCEG score recompute
  4. 2026-10-08 17:14 UTCEPSS rescore
  5. 2026-10-08 11:53 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-06 15:33 UTCEG score recompute
  8. 2026-10-06 15:19 UTCEPSS rescore
  9. 2026-10-05 20:26 UTCEG score recompute
  10. 2026-10-05 19:22 UTCEG score recompute
  11. 2026-10-05 18:23 UTCEG score recompute
  12. 2026-10-05 17:56 UTCEG score recompute
  13. 2026-10-05 17:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-93319?
CVE-2026-93319 is a medium vulnerability published on October 5, 2026. A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.
When was CVE-2026-93319 disclosed?
CVE-2026-93319 was first published on October 5, 2026, with the most recent update on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93319 actively exploited?
CVE-2026-93319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93319?
CVE-2026-93319 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93319?
A fix for CVE-2026-93319 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-93319

Explore →

Is Your Infrastructure Affected by CVE-2026-93319?

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

Book a Demo →Browse All CVEs