Home/CVE/BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. T
CVE
CVE-2024-23651
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. T
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.
HIGH · CVSS 8.7
EPSS 0.00548
Act now
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2024-23651, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
2Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
2Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
1mobyproject buildkit< 0.12.5
▤
Affected Packages
8Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Go
github.com/moby/buildkit
HIGH
fixed in 0.12.5
Ubuntu:20.04:LTS
docker.io
Ubuntu:20.04:LTS
docker.io-app
Ubuntu:22.04:LTS
docker.io
Ubuntu:22.04:LTS
docker.io-app
Ubuntu:24.04:LTS
docker.io
Ubuntu:24.04:LTS
docker.io-app
Ubuntu:Pro:18.04:LTS
docker.io
⚠
Public Exploits & PoCs
9These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted.
📦
Fixed versions by distribution
19The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgebuildkit fixed in 0.12.5-r0
alpine edgedocker fixed in 25.0.2-r0
alpine edgepodman fixed in 4.9.2-r0
alpine edgesingularity fixed in 4.1.1-r0
alpine v3.19buildkit fixed in 0.12.5-r0
alpine v3.19docker fixed in 25.0.2-r0
alpine v3.19singularity fixed in 4.1.1-r0
alpine v3.20buildkit fixed in 0.12.5-r0
alpine v3.20docker fixed in 25.0.2-r0
alpine v3.20podman fixed in 4.9.2-r0
alpine v3.20singularity fixed in 4.1.1-r0
suse sle15buildah fixed in 0:1.35.4-150300.8.25.1
suse sle15docker fixed in 0:24.0.7_ce-150000.193.1
suse sle15docker-bash-completion fixed in 0:24.0.7_ce-150000.193.1
suse sle15docker-fish-completion fixed in 0:25.0.6_ce-150000.207.1
suse sle15docker-rootless-extras fixed in 0:25.0.6_ce-150000.207.1
suse sle15docker-stable fixed in 0:24.0.9_ce-150000.1.25.1
suse sle15docker-stable-bash-completion fixed in 0:24.0.9_ce-150000.1.25.1
suse sle15docker-stable-zsh-completion fixed in 0:24.0.9_ce-150000.1.25.1
▣
Scoring & Timeline
8.7
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
15suse-csafSUSE-SU-2025:03545-1
suse-csafSUSE-SU-2025:03540-1
suse-csafopenSUSE-SU-2025:15589-1
usnUSN-7474-1
suse-csafSUSE-SU-2025:20056-1
🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.