BuildKit vulnerable to malicious frontend causing file escape outside of storage root
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-33747
PublishedBuildKit 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.
- Source published
- 27 Mar 2026 00:49:06 UTC
- Source modified
- 27 Mar 2026 19:59:06 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
euvd · EUVD-2026-16518
PublishedBuildKit 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Mar 27, 2026, 12:49:06 AM
dateUpdated: Mar 27, 2026, 7:59:06 PM
26 related source bulletins · separate from aliases
RHSA-2026:9440: Red Hat Security Advisory: Red Hat OpenShift Service Mesh 3.0.10
CVE-2026-25679 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748
openSUSE-SU-2026:10472-1: conftest-0.67.1-2.1 on GA media
CVE-2026-33747
openSUSE-SU-2026:11075-1: docker-stable-24.0.9_ce-18.1 on GA media
CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-33997 · CVE-2026-34040 · CVE-2026-39821 · CVE-2026-41567
RHSA-2026:57013: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20.17 security, enhancement & bug fix update
CVE-2025-61726 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-6734 · CVE-2026-9697 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-44740 · CVE-2026-45736 · CVE-2026-48779 · CVE-2026-53488 · CVE-2026-53489 · CVE-2026-53492 · CVE-2026-59869
RHSA-2026:51033: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2024-25621 · CVE-2025-61726 · CVE-2025-61728 · CVE-2025-61729 · CVE-2025-66506 · CVE-2025-68121 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-42306 · CVE-2026-42499 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-53488 · CVE-2026-53492
RHSA-2026:37387: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.0 security, enhancement & bug fix update
CVE-2024-25621 · CVE-2024-40635 · CVE-2024-45310 · CVE-2025-8766 · CVE-2025-21613 · CVE-2025-21614 · CVE-2025-22870 · CVE-2025-47911 · CVE-2025-52881 · CVE-2025-54410 · CVE-2025-58058 · CVE-2025-64329 · CVE-2025-66506 · CVE-2026-22772 · CVE-2026-23831 · CVE-2026-24117 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-25934 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27903 · CVE-2026-33540 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33814 · CVE-2026-34986 · CVE-2026-35172 · CVE-2026-35469 · CVE-2026-39821 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39883 · CVE-2026-41506 · CVE-2026-41567 · CVE-2026-41568 · CVE-2026-42502 · CVE-2026-42506 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-45571 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46598
SUSE-SU-2026:2120-1: Security update for docker-stable
CVE-2026-33747 · CVE-2026-33748
openSUSE-SU-2026:20809-1: Security update for trivy
CVE-2025-64702 · CVE-2025-69725 · CVE-2026-25934 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-39984 · CVE-2026-41506
openSUSE-SU-2026:10456-1: tailscale-1.96.4-1.1 on GA media
CVE-2026-33747
RHSA-2026:10125: Red Hat Security Advisory: RHTAS 1.3.4 - Red Hat Trusted Artifact Signer Release
CVE-2025-68121 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-33186 · CVE-2026-33211 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986
openSUSE-SU-2026:10651-1: trivy-0.70.0-1.1 on GA media
CVE-2025-69725 · CVE-2026-25934 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-39984
RHSA-2026:26568: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2026-25679 · CVE-2026-27137 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33810 · CVE-2026-34986
openSUSE-SU-2026:20814-1: Security update for docker-stable
CVE-2026-33747 · CVE-2026-33748
openSUSE-SU-2026:22203-1: Security update for tailscale
CVE-2026-33747
SUSE-SU-2026:21851-1: Security update for docker-stable
CVE-2026-33747 · CVE-2026-33748
RHSA-2026:9453: Red Hat Security Advisory: Red Hat OpenShift Service Mesh 3.2.4
CVE-2026-25679 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986
RHSA-2026:46885: Red Hat Security Advisory: multicluster engine for Kubernetes v2.10.4 security update
CVE-2025-58183 · CVE-2026-16242 · CVE-2026-17107 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-59869
SUSE-SU-2026:2578-1: Security update for docker-stable
CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33997 · CVE-2026-34040
WID-SEC-W-2026-0873: docker: Mehrere Schwachstellen
CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33997 · CVE-2026-34040
RHSA-2026:22465: Red Hat Security Advisory: Red Hat Quay 3.17.2
CVE-2025-62718 · CVE-2026-4427 · CVE-2026-27459 · CVE-2026-29063 · CVE-2026-29074 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-32286 · CVE-2026-32589 · CVE-2026-32590 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33894 · CVE-2026-34986 · CVE-2026-39892 · CVE-2026-40192 · CVE-2026-40895 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42039 · CVE-2026-42041 · CVE-2026-42043 · CVE-2026-42044 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496
RHSA-2026:9448: Red Hat Security Advisory: Red Hat OpenShift Service Mesh 3.1.7
CVE-2026-25679 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986
RHSA-2026:70267: Red Hat Security Advisory: Red Hat Quay 3.14.9
CVE-2026-4427 · CVE-2026-6322 · CVE-2026-9277 · CVE-2026-10143 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-15792 · CVE-2026-15927 · CVE-2026-16221 · CVE-2026-18255 · CVE-2026-32591 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33818 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39822 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39835 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42499 · CVE-2026-42504 · CVE-2026-42508 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44705 · CVE-2026-44990 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-48526 · CVE-2026-49477 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-56852 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-57231 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-84375
RHSA-2026:42644: Red Hat Security Advisory: RHOAI 2.25.9 - Red Hat OpenShift AI
CVE-2024-12224 · CVE-2025-14920 · CVE-2025-14921 · CVE-2025-14924 · CVE-2025-14926 · CVE-2025-14927 · CVE-2025-14928 · CVE-2025-14929 · CVE-2025-14930 · CVE-2025-69227 · CVE-2025-69228 · CVE-2026-5241 · CVE-2026-8643 · CVE-2026-11816 · CVE-2026-22773 · CVE-2026-22807 · CVE-2026-23490 · CVE-2026-24486 · CVE-2026-24779 · CVE-2026-25048 · CVE-2026-25681 · CVE-2026-25960 · CVE-2026-25990 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-27893 · CVE-2026-28356 · CVE-2026-28684 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-32597 · CVE-2026-32981 · CVE-2026-33186 · CVE-2026-33236 · CVE-2026-33699 · CVE-2026-33747 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-34478 · CVE-2026-34480 · CVE-2026-34993 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39892 · CVE-2026-42499 · CVE-2026-42504 · CVE-2026-42578 · CVE-2026-42581 · CVE-2026-42584 · CVE-2026-42587 · CVE-2026-43868 · CVE-2026-43869 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44660 · CVE-2026-48526 · CVE-2026-48746 · CVE-2026-54293
RHSA-2026:30650: Red Hat Security Advisory: multicluster engine for Kubernetes v2.8.8 security update
CVE-2025-47914 · CVE-2025-58183 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-34986 · CVE-2026-35206 · CVE-2026-39821 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-46595
RHSA-2026:47388: Red Hat Security Advisory: multicluster engine for Kubernetes v2.10.4 security update
CVE-2025-58183 · CVE-2026-16242 · CVE-2026-17107 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33811 · CVE-2026-34986 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39835 · CVE-2026-42508 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-59869
RHSA-2026:29854: Red Hat Security Advisory: Red Hat OpenShift API for Data Protection
CVE-2025-68121 · CVE-2026-25679 · CVE-2026-27137 · CVE-2026-32280 · CVE-2026-32281 · CVE-2026-32282 · CVE-2026-33186 · CVE-2026-33747 · CVE-2026-33748 · CVE-2026-33810 · CVE-2026-34986
- Source published
- Mar 27, 2026, 12:49:06 AM (timezone not stated)
- Source modified
- Mar 27, 2026, 7:59:06 PM (timezone not stated)
- Saved here
- 15 Nov 2026 10:04:37 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd · CVE-2026-33747
PublishedBuildKit 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-22
Original publisher date fields
published: 2026-03-27T01:16:21.330
lastModified: 2026-06-17T10:38:01.807
1 source CPE criteria · context only
- cpe:2.3:a:mobyproject:buildkit:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 27 Mar 2026 01:16:21 UTC
- Source modified
- 17 Jun 2026 10:38:01 UTC
- Saved here
- 25 Oct 2026 08:17:24 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 · [email protected] · Primary · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
osv · GHSA-4c29-8rgm-jvjj
Published### Impact 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. ### Patches The issue has been fixed in v0.28.1+ ### Workarounds Issue 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.
- Source published
- 26 Mar 2026 18:26:09 UTC
- Source modified
- 10 Sep 2026 03:50:37 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Publisher rating · HIGH
osv · GO-2026-4858
PublishedBuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit
- Source published
- 27 Mar 2026 18:39:44 UTC
- Source modified
- 28 Mar 2026 15:59:16 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.