An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.
CVE-2026-93317
MEDIUMPre-NVD 5.95.9
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 5.9Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMlow confidence
- EG Risk
- 27EG Risk 27/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 computedSeverity59% × 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
- —
- EPSS %ILE
- —
- 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 5, 2026
Advisory Details (2)
Auto-updated Oct 5, 2026Patch available. Sources: github_release, github.
githubMentions a patch (unverified)
Container blob cache can accept unverified content · Advisory · moby/buildkit · GitHub
Affected: v0.32.3+
https://github.com/moby/buildkit/security/advisories/GHSA-p3rc-w3hc-pqvvgithub_release Patch Available
v0.33.1
Patch available: moby/buildkit v0.33.1
https://github.com/moby/buildkit/releases/tag/v0.33.1Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-10-05 20:26 UTCEG score recompute
- 2026-10-05 19:22 UTCEG score recompute
- 2026-10-05 18:23 UTCEG score recompute
- 2026-10-05 17:46 UTCEG score recompute
- 2026-10-05 17:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-93317?
CVE-2026-93317 is a medium vulnerability published on October 5, 2026. An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.
When was CVE-2026-93317 disclosed?
CVE-2026-93317 was first published on October 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-93317?
CVE-2026-93317 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-93317?
A fix for CVE-2026-93317 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-93317
Is Your Infrastructure Affected by CVE-2026-93317?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.