Authenticated file escape via upload path traversal
Published Jul 21, 2026 · Updated Jul 21, 2026
Path traversal in the BuildKit daemon before 0.31.2 allows attackers to place uploaded files outside its controlled state directory. The local-source upload handler accepts a client-supplied destination path without reliably confining its resolved target beneath the daemon-managed state root. Exploitation requires permission to issue builds through the control API and an untrusted custom client; standard Docker Buildx and buildctl requests do not expose the path.
Summary
What happened
Path traversal in the BuildKit daemon before 0.31.2 allows attackers to place uploaded files outside its controlled state directory. The local-source upload handler accepts a client-supplied destination path without reliably confining its resolved target beneath the daemon-managed state root. Exploitation requires permission to issue builds through the control API and an untrusted custom client; standard Docker Buildx and buildctl requests do not expose the path.
The record
- CVE
- CVE-2026-15789
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- Moby Project
- Product
- BuildKit
- Classifications
- CWE-22, T1105
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 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 <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