CVE-2024-23652Critical· 10.0▾ AbyssalPoC availableBuildKit vulnerable to possible host system access from mount stub cleaner
▾ Abyssal zone — Critical with a public exploit or in-the-wild use
impact 55 · likelihood 0.5 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 1 source. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
2.1%
2.1% → 2.5%
2 GitHub repos (last check)
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
Avoid using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing RUN --mount feature.
github.com/moby/buildkit < 0.12.5Upgrade to a patched release:
github.com/moby/buildkit 0.12.5Connected by shared product, vendor, weakness, or advisory.
CVE-2021-41091Medium· 5.9Moby (Docker Engine) Insufficiently restricted permissions on data directory
CVE-2026-61801Medium· 5.5The `github.com/moby/sys/user` package provides Go utilities for parsing and looking up entries in Unix-style user and group database files
CVE-2026-93315Medium· 5.8When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup
CVE-2026-93321Medium· 6.9A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.
CVE-2026-93326Medium· 6.0A build step for a Git source, crafted in a specific way, can bypass some policy validation rules
CVE-2026-93320Medium· 6.0BuildKit may be tricked into performing file actions with special file inodes where regular files are expected