CVE-2026-33747

HIGHNVD 9.88.4
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.4 under the CNA's CVSS (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: cna:github_m
Trending — Patch released this week
8.4EG
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
8.4(low)
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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

March 27, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jul 27, 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

Vendor Advisories for CVE-2026-33747(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17836154322026-07-21redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatmulticluster-engine/must-gather-rhel9:17821587982026-06-28redhat
redhatoadp/oadp-mustgather-rhel9:17797700492026-06-25redhat
redhatoadp/oadp-mustgather-rhel9:17797700572026-06-17redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatrhtas/client-server-rhel9:17763390992026-04-23redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17762403922026-04-21redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17763154662026-04-21redhat
redhatopenshift-service-mesh/istio-proxyv2-rhel9:17762915402026-04-21redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 3× 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-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 12:50 UTCEG score recompute
  3. 2026-07-27 12:50 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33747?
CVE-2026-33747 is a high 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 60.2% 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). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.4. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs