# CVE-2026-75593: BuildKit: Malicious client can bypass destination directory validation on local sources upload

> A malicious client with API access can bypass directory validation to read or modify files outside the intended build context in BuildKit.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** AZL-97035, GHSA-wqjv-cjqw-p7p5

## What is CVE-2026-75593?

CVE-2026-75593 is a high-severity path traversal vulnerability in moby buildkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to 0.31.2, 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 BuildKit control API to issue builds, eg., bypass authentication, etc. This issue is fixed in version 0.31.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-75593?


## How do I fix CVE-2026-75593?

Upgrade to a fixed version.

## Is CVE-2026-75593 being exploited?

There is no known exploitation of CVE-2026-75593 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75593 and fix it if it is affected.

What it is: CVE-2026-75593 is a high-severity path traversal vulnerability in moby buildkit, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75593 in the wild and no public exploit code.

Affected product: moby buildkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75593/ (Markdown: https://insights.sbomify.com/CVE-2026-75593/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75593
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75593
- OSV: https://osv.dev/vulnerability/CVE-2026-75593

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75593/
Summaries are generated and may contain mistakes; the official description above is the record.