Approved changes feed: RSS · Atom

cpe:2.3:a:mobyproject:buildkit:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorMobyproject (6ca703fa-9c4f-5fa7-9a39-46916d79f1a4)
ProductBuildkit (5b3d9e2a-5ddb-5615-8c2c-ed3ff0b65e4b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/moby/buildkit purl2cpe 2026-06-01 10:16:15.150510
pkg:golang/github.com/moby/buildkit purl2cpe 2026-06-01 10:16:15.150512

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-33748 vulnerable 2026-06-08 07:59:10.693604 BuildKit Git URL subdir component can cause access to restricted files
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, insufficient validation of Git URL fragment subdir components may allow access to files outside the checked-out Git repository root. Possible access is limited to files on the same mounted filesystem. The issue has been fixed in version v0.28.1 The issue affects only builds that use Git URLs with a subpath component. As a workaround, avoid building Dockerfiles from untrusted sources or using the subdir component from an untrusted Git repository where the subdir component could point to a symlink.
Published: 2026-03-27T14:00:21.200Z
Updated: 2026-03-27T19:58:28.764Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-33747 vulnerable 2026-06-08 07:59:10.693107 BuildKit vulnerable to malicious frontend causing file escape outside of storage root
HIGH (8.4)
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.
Published: 2026-03-27T00:49:06.165Z
Updated: 2026-03-27T19:59:06.907Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-23653 vulnerable 2026-06-08 06:29:40.091394 BuildKit interactive containers API does not validate entitlements check
CRITICAL (9.8)
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.
Published: 2024-01-31T22:03:56.667Z
Updated: 2024-08-23T18:16:30.503Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-23652 vulnerable 2026-06-08 06:29:40.090878 BuildKit possible host system access from mount stub cleaner
CRITICAL (10)
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. A malicious BuildKit frontend or Dockerfile using RUN --mount could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. The issue has been fixed in v0.12.5. Workarounds include avoiding using BuildKit frontends from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
Published: 2024-01-31T21:57:42.774Z
Updated: 2025-06-17T21:29:21.838Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-23651 vulnerable 2026-06-08 06:29:40.090337 BuildKit possible race condition with accessing subpaths from cache mounts
HIGH (8.7)
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container. The issue has been fixed in v0.12.5. Workarounds include, avoiding using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with --mount=type=cache,source=... options.
Published: 2024-01-31T21:49:18.041Z
Updated: 2025-05-29T15:03:12.436Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-23650 vulnerable 2026-06-08 06:29:40.089618 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-26054 vulnerable 2026-06-08 05:57:37.944508 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.