CVE-2026-33747

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% 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
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, when using a custom BuildKit frontend, the frontend can craft an API message that causes files to be written outside of the BuildKit state directory for the execution context. The issue has been fixed in v0.28.1. The vulnerability requires using an untrusted BuildKit frontend set with #syntax or --build-arg BUILDKIT_SYNTAX. Using these options with a well-known frontend image like docker/dockerfile is not affected.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

March 27, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github_release, github.
github Patch Available

Malicious frontend can cause file escape outside of storage root · Advisory · moby/buildkit · GitHub

Affected: v0.28.1+

https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj
github_release Patch Available

v0.28.1

Patch available: moby/buildkit v0.28.1

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

Patch Availability(12)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
docker.io20.10.10+dfsg1-1 ... 28.5.2+dfsg4-3 (61 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
docker.io20.10.24+dfsg1-1 ... 28.5.2+dfsg4-4 (46 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
docker.io26.1.5+dfsg1-926.1.5+dfsg1-9+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
docker.io26.1.5+dfsg1-10 ... 28.5.2+dfsg4-2 (19 versions)28.5.2+dfsg4-3
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/moby/buildkit0.28.1

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-02 13:14 UTCOSV refresh
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 14:17 UTCEPSS rescore
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 70 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 10:03 UTCEG score recompute
  7. 2026-08-16 10:03 UTCVendor advisory
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 23:21 UTCVendor advisory
  11. 2026-08-14 19:15 UTCVendor advisory
  12. 2026-08-14 14:34 UTCVendor advisory
  13. 2026-08-14 10:28 UTCVendor advisory
  14. 2026-08-14 06:21 UTCEG score recompute
  15. 2026-08-14 06:21 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 04:52 UTCVendor advisory
  18. 2026-08-13 00:45 UTCVendor advisory
  19. 2026-08-12 20:39 UTCEG score recompute
  20. 2026-08-12 20:39 UTCVendor advisory
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-12 00:55 UTCVendor advisory
  23. 2026-08-11 20:48 UTCEG score recompute
  24. 2026-08-11 20:48 UTCVendor advisory
  25. 2026-08-11 07:56 UTCVendor advisory
  26. 2026-08-11 03:49 UTCEG score recompute
  27. 2026-08-11 03:49 UTCVendor advisory
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 09:39 UTCVendor advisory
  30. 2026-08-10 05:33 UTCVendor advisory
  31. 2026-08-10 01:26 UTCVendor advisory
  32. 2026-08-09 21:18 UTCVendor advisory
  33. 2026-08-09 17:12 UTCEG score recompute
  34. 2026-08-09 17:12 UTCVendor advisory
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 13:05 UTCVendor advisory
  37. 2026-08-09 05:54 UTCEG score recompute
  38. 2026-08-09 05:54 UTCVendor advisory
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 08:47 UTCVendor advisory
  41. 2026-08-08 04:40 UTCVendor advisory
  42. 2026-08-08 00:34 UTCVendor advisory
  43. 2026-08-07 20:27 UTCEG score recompute
  44. 2026-08-07 20:27 UTCVendor advisory
  45. 2026-08-07 16:21 UTCVendor advisory
  46. 2026-08-06 18:44 UTCEG score recompute
  47. 2026-08-06 18:44 UTCVendor advisory
  48. 2026-08-06 13:46 UTCEPSS rescore
  49. 2026-08-06 09:03 UTCVendor advisory
  50. 2026-08-06 04:56 UTCVendor advisory
  51. 2026-08-06 00:49 UTCEG score recompute
  52. 2026-08-06 00:49 UTCVendor advisory
  53. 2026-08-05 19:17 UTCEPSS rescore
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-04 03:58 UTCVendor advisory
  57. 2026-08-03 23:12 UTCEG score recompute
  58. 2026-08-03 23:12 UTCVendor advisory
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-02 23:27 UTCVendor advisory
  61. 2026-08-02 19:20 UTCVendor advisory
  62. 2026-08-02 15:14 UTCEG score recompute 1.40
  63. 2026-08-02 15:14 UTCVendor advisory
  64. 2026-08-02 02:27 UTCEPSS rescore
  65. 2026-08-01 04:16 UTCEPSS rescore
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-27 14:13 UTCEPSS rescore
  69. 2026-07-27 12:50 UTCEG score recompute
  70. 2026-07-27 12:50 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-33747?
CVE-2026-33747 is a critical vulnerability published on March 27, 2026. BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, when using a custom BuildKit frontend, the frontend can craft an API message that causes files to be written outside of the BuildKit state directory for…
When was CVE-2026-33747 disclosed?
CVE-2026-33747 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33747 actively exploited?
CVE-2026-33747 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 58.8% of all scored CVEs.
What is the CVSS score of CVE-2026-33747?
CVE-2026-33747 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-33747?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33747, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33747

Explore →

Is Your Infrastructure Affected by CVE-2026-33747?

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