Host file deletion via unchecked mount cleanup
Published Jan 31, 2024 · Updated Jun 17, 2025
Path traversal in Moby BuildKit before 0.12.5 allows remote attackers to delete host files through a malicious build definition. MountStubsCleaner records mountpoint paths before a build and later cleans them without re-resolving each path beneath the build root after container execution. Exploitation requires an untrusted frontend or Dockerfile using RUN --mount; successful cleanup can delete files or directories outside the container.
Summary
What happened
Path traversal in Moby BuildKit before 0.12.5 allows remote attackers to delete host files through a malicious build definition. MountStubsCleaner records mountpoint paths before a build and later cleans them without re-resolving each path beneath the build root after container execution. Exploitation requires an untrusted frontend or Dockerfile using RUN --mount; successful cleanup can delete files or directories outside the container.
The record
- CVE
- CVE-2024-23652
- Published
- Jan 31, 2024
- Updated
- Jun 17, 2025
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-22, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.12.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo