CVE-2026-93315 BuildKit proxy CA cleanup can be disrupted by build steps
Medium 5.8
Published
Updated
Check this codebase for CVE-2026-93315 and fix it if it is affected.
What it is: CVE-2026-93315 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93315 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-93315/ (Markdown: https://insights.sbomify.com/CVE-2026-93315/index.md)
Attackers can disrupt BuildKit proxy CA cleanup via race conditions, potentially blocking builds or bypassing security controls.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-93315?
CVE-2026-93315 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup. This may cause cleanup to block, operate outside the build rootfs, or fail without failing the build.
Weakness: CWE-367
Which versions are affected by CVE-2026-93315?
How do I fix CVE-2026-93315?
Apply the vendor's patch.
Is CVE-2026-93315 being exploited?
There is no known exploitation of CVE-2026-93315 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-93315, GHSA-2f5p-x9ph-g97x, UBUNTU-CVE-2026-93315.