cve.bz

CVE-2026-93323 moby buildkit

6.8 mediumEPSS 0.1%

Medium (6.8) in moby buildkit. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit. A build context containing an oversized file could make buildkitd allocate memory proportional to that file, potentially exhausting memory and terminating the daemon, which interrupts other builds on the same instance. Fixed by rejecting such files above 16 MiB.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-93323 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93323?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93323?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93323 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
moby BuildKitthrough 0.33.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 moredocker.io, docker.io-appno fix listedUBUNTU-CVE-2026-93323
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-93323
Azure Linux3docker-buildxno fix listedAZL-106746
Azure Linux3moby-engine25.0.18-1AZL-106824

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in BuildKit's Dockerfile frontend when processing build contexts. The frontend loads Dockerfile and .dockerignore files directly into memory without enforcing an upper size limit. An authenticated user authorized to submit builds can provide an excessively large Dockerfile or .dockerignore file, forcing the `buildkitd` daemon to allocate memory proportional to the file size. This unbounded allocation can exhaust host or container memory limits and trigger an out-of-memory termination of the daemon process, crashing active builds running on shared instances.

Red Hat's mitigation

Enforce file size limits in source control or CI/CD pre-commit hooks to reject Dockerfile and .dockerignore files exceeding 16 MiB prior to build submission, and restrict build execution privileges to trusted users.

ProductPackageStateAdvisory
Red Hat Hardened ImagesbuildahNot affected
Red Hat Hardened ImagespodmanNot affected
Red Hat Hardened ImagestrivyNot affected
Red Hat Quay 3quay/quay-builder-rhel8Fix deferred
Red Hat Quay 3quay/quay-builder-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-93323.

References

Check your stackJSON