Authenticated file writes via unchecked upload destination
Published Aug 19, 2026 · Updated Aug 25, 2026
Path traversal in Moby BuildKit before 0.31.2 allows remote authenticated users to write files outside its state directory. The local-source upload handler accepts a custom request destination without ensuring the resolved path remains under the BuildKit-controlled state directory. Exploitation requires permission to issue builds through the BuildKit control API, and the reported consequence is unauthorized file modification or deletion.
Summary
What happened
Path traversal in Moby BuildKit before 0.31.2 allows remote authenticated users to write files outside its state directory. The local-source upload handler accepts a custom request destination without ensuring the resolved path remains under the BuildKit-controlled state directory. Exploitation requires permission to issue builds through the BuildKit control API, and the reported consequence is unauthorized file modification or deletion.
The record
- CVE
- CVE-2026-75593
- Published
- Aug 19, 2026
- Updated
- Aug 25, 2026
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record 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.31.2
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