BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.2, a custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. The client needs to have valid permissions to access BuildKit control API to issue builds, eg., bypass authentication, etc. This issue is fixed in version 0.31.2.
CVE-2026-75593
This high-severity CVE scores 7.2 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(low)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
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 computedSeverity72% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026v0.31.2
Patch available: moby/buildkit v0.31.2
https://github.com/moby/buildkit/releases/tag/v0.31.2Malicious client can bypass destination directory validation on local sources upload · Advisory · moby/buildkit · GitHub
https://github.com/moby/buildkit/security/advisories/GHSA-g2h8-426c-7976Vendor Advisories for CVE-2026-75593(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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-08-20 22:56 UTCEPSS rescore
- 2026-08-20 20:06 UTCGHSA enrichment
- 2026-08-20 08:12 UTCGHSA enrichment
- 2026-08-19 20:19 UTCEG score recompute
- 2026-08-19 20:13 UTCEG score recompute
- 2026-08-19 20:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75593?
When was CVE-2026-75593 disclosed?
Is CVE-2026-75593 actively exploited?
What is the CVSS score of CVE-2026-75593?
How do I remediate CVE-2026-75593?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75593
Is Your Infrastructure Affected by CVE-2026-75593?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.