# CVE-2024-23651: BuildKit possible race condition with accessing subpaths from cache mounts

> A race condition in BuildKit allows malicious parallel build steps to access host system files via shared cache mounts.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** AZL-34085, AZL-35005, BELL-CVE-2024-23651, CLEANSTART-2025-MU54155, CLEANSTART-2026-HB39475, GHSA-m3r6-h7wv-7xxv, GO-2024-2493, UBUNTU-CVE-2024-23651

## What is CVE-2024-23651?

CVE-2024-23651 is a high-severity vulnerability in moby buildkit, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-23651?

3 open source packages ship an affected version, including github.com/moby/buildkit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/moby/buildkit` | Go | All versions | 0.12.5 |
| `github.com/moby/buildkit` | Go | All versions | 0.12.5 |
| `github.com/moby/buildkit` | Go | All versions | 0.12.5 |

Products: Mobyproject Buildkit.

## How do I fix CVE-2024-23651?

Upgrade github.com/moby/buildkit to 0.12.5 or later.

## Is CVE-2024-23651 being exploited?

There is no known exploitation of CVE-2024-23651 in the wild and no public exploit code.

## Other vulnerabilities in moby buildkit

- [CVE-2024-23652](https://insights.sbomify.com/CVE-2024-23652/): BuildKit possible host system access from mount stub cleaner (critical 10.0)
- [CVE-2024-23653](https://insights.sbomify.com/CVE-2024-23653/): BuildKit interactive containers API does not validate entitlements check (critical 9.8)
- [CVE-2026-33747](https://insights.sbomify.com/CVE-2026-33747/): BuildKit vulnerable to malicious frontend causing file escape outside of storage root (high 8.4)
- [CVE-2026-33748](https://insights.sbomify.com/CVE-2026-33748/): BuildKit Git URL subdir component can cause access to restricted files (high 8.2)
- [CVE-2026-15789](https://insights.sbomify.com/CVE-2026-15789/): Malicious client can bypass destination directory validation on local sources upload (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23651 and fix it if it is affected.

What it is: CVE-2024-23651 is a high-severity vulnerability in moby buildkit, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23651 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/moby/buildkit (Go): affected all versions; fixed in 0.12.5
- github.com/moby/buildkit (Go): affected all versions; fixed in 0.12.5
- github.com/moby/buildkit (Go): affected all versions; fixed in 0.12.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23651/ (Markdown: https://insights.sbomify.com/CVE-2024-23651/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23651
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23651
- OSV: https://osv.dev/vulnerability/CVE-2024-23651

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23651/
Summaries are generated and may contain mistakes; the official description above is the record.