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.
id: GO-ID-PENDING
modules:
- module: github.com/moby/buildkit
versions:
- fixed: 0.28.1
vulnerable_at: 0.28.0
summary: BuildKit's Malicious frontend can cause file escape outside of storage root in github.com/moby/buildkit
cves:
- CVE-2026-33747
ghsas:
- GHSA-4c29-8rgm-jvjj
references:
- advisory: https://github.com/advisories/GHSA-4c29-8rgm-jvjj
- advisory: https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj
- web: https://github.com/moby/buildkit/releases/tag/v0.28.1
source:
id: GHSA-4c29-8rgm-jvjj
created: 2026-03-26T19:01:41.791309817Z
review_status: UNREVIEWED
Advisory GHSA-4c29-8rgm-jvjj references a vulnerability in the following Go modules:
Description:
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
#syntaxor--build-arg BUILDKIT_SYNTAX. Using these options with a well-known frontend image likedocker/dockerfileis not affected.References:
Cross references:
See doc/quickstart.md for instructions on how to triage this report.