CVE-2026-15789

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. 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, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 the BuildKit control API to issue builds, e.g., bypass authentication, etc.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 21, 2026
Patch available. Sources: github.
github Patch Available

Malicious client can bypass destination directory validation on local sources upload · Advisory · moby/buildkit · GitHub

https://github.com/moby/buildkit/security/advisories/GHSA-g2h8-426c-7976

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 52× 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-08-30 02:17 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 22:32 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 23:08 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 00:44 UTCEG score recompute
  9. 2026-08-25 13:48 UTCEPSS rescore
  10. 2026-08-24 14:54 UTCEG score recompute
  11. 2026-08-23 05:02 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 06:38 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 08:12 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 22:36 UTCEG score recompute
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 20:32 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 20:56 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 22:33 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:21 UTCEG score recompute
Show 48 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 01:46 UTCEG score recompute
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 03:24 UTCEG score recompute
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-12 17:49 UTCEG score recompute
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-11 19:25 UTCEG score recompute
  9. 2026-08-11 13:42 UTCEPSS rescore
  10. 2026-08-11 08:13 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-09 22:39 UTCEG score recompute
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-08 01:52 UTCEG score recompute
  15. 2026-08-06 16:16 UTCEG score recompute
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-06 05:05 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-04 19:28 UTCEG score recompute
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:38 UTCEPSS rescore
  22. 2026-08-03 21:01 UTCEG score recompute
  23. 2026-08-03 10:35 UTCEPSS rescore
  24. 2026-08-02 11:25 UTCEG score recompute
  25. 2026-08-02 02:26 UTCEPSS rescore
  26. 2026-08-01 13:01 UTCEG score recompute
  27. 2026-08-01 04:15 UTCEPSS rescore
  28. 2026-07-31 03:22 UTCEG score recompute
  29. 2026-07-30 16:10 UTCEG score recompute▲ 0.60
  30. 2026-07-30 16:09 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  31. 2026-07-30 03:56 UTCEG score recompute
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-29 05:37 UTCEG score recompute
  34. 2026-07-28 07:17 UTCEG score recompute
  35. 2026-07-27 14:13 UTCEPSS rescore
  36. 2026-07-27 08:49 UTCEG score recompute
  37. 2026-07-26 14:54 UTCEPSS rescore
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-26 10:30 UTCEG score recompute
  40. 2026-07-25 14:17 UTCEPSS rescore
  41. 2026-07-24 14:17 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 03:05 UTCEG score recompute
  44. 2026-07-22 23:07 UTCEG score recompute
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-21 17:20 UTCEG score recompute
  47. 2026-07-21 16:29 UTCEG score recompute
  48. 2026-07-21 16:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15789?
CVE-2026-15789 is a high vulnerability published on July 21, 2026. 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 the BuildKit control API to issue builds, e.g., bypass authentication, etc.
When was CVE-2026-15789 disclosed?
CVE-2026-15789 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15789 actively exploited?
CVE-2026-15789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.3% of all scored CVEs.
What is the CVSS score of CVE-2026-15789?
CVE-2026-15789 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-15789?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15789, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15789?

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

Start Free Scan →Browse All CVEs