cve.bz

CVE-2026-93319 moby buildkit

5.7 mediumEPSS 0.09%

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

On this page
A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

Severity

CVSS 4.0

5.7 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.09% (unchanged from 0.09% a week ago; 0.09% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th 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-567 Unsynchronized Access to Shared Data in a Multithreaded Context
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-93319 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93319?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93319?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-93319 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-93319
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-93319
Azure Linux3moby-engineno fix listedAZL-106809

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 denial of service flaw was found in BuildKit's internal API request handling. An attacker utilizing a malicious external build frontend can transmit a specific sequence of requests via the internal API to induce a data race condition within the daemon. This concurrency race triggers an unhandled Go runtime panic, causing the `buildkitd` daemon process to crash abruptly and terminating all active and concurrent build operations running on the shared builder instance.

Red Hat's mitigation

Restrict builds to trusted internal frontends by avoiding untrusted `#syntax` image directives or custom `--frontend` flags. Isolate multi-tenant build environments onto dedicated, single-tenant worker nodes to prevent shared daemon disruption.

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-93319.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON