CVE-2026-15789
Received Received - Intake

BuildKit Daemon File Escape Vulnerability

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: Docker Inc.

Description
A custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. The client needs to have valid permissions to access the BuildKit control API to issue builds, e.g., bypass authentication, etc.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-21
AI Q&A
2026-07-21
EPSS Evaluated
N/A
NVD
CVE-2026-15789
EUVD
EUVD-2026-46309

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
docker buildkit to 0.31.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability allows a malicious client with valid permissions to bypass directory restrictions when uploading files to the BuildKit daemon. It enables path traversal, letting files escape the controlled state directory. The issue affects BuildKit versions up to v0.31.1 and has been patched in v0.31.2 and later.

Detection Guidance

Check BuildKit version with 'buildkitd --version' or 'docker buildx version'. If version is below v0.31.2, the system is vulnerable. Inspect build logs for unexpected file writes outside expected directories.

Impact Analysis

If exploited, this vulnerability could allow unauthorized file access or modification outside the intended directory. This may lead to data leaks, system compromise, or unauthorized changes to sensitive files. The risk is limited to scenarios where untrusted parties can issue builds on a BuildKit service.

Compliance Impact

This vulnerability could lead to unauthorized access or exposure of sensitive data, potentially violating GDPR, HIPAA, or other regulations. Compliance may be impacted if the vulnerability results in data breaches or unauthorized file access.

Mitigation Strategies

Upgrade BuildKit to v0.31.2 or later. Ensure only trusted clients like Docker Buildx or Buildctl access the BuildKit control API. Enforce strict authentication for all build requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15789. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart