cve.bz

CVE-2026-93321 moby buildkit: Improper Validation of Array Index

6.9 mediumEPSS 0.2%

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

On this page
A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th 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-06. 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-129 Improper Validation of Array Index
OWASP Top 10
A05:2025 Injection
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-93321 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93321?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93321?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-93321 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-93321
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-93321
Azure Linux3moby-engineno fix listedAZL-106821
Alpaquita25dockerno fix listedBELL-CVE-2026-93321
Alpaquitastreamdocker29.9.0-r0BELL-CVE-2026-93321

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

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A denial of service flaw was found in BuildKit's low-level builder (LLB) definition processing subsystem. The `buildkitd` daemon fails to properly validate input parameters and array indices within submitted LLB definitions. A malicious build frontend can supply a crafted LLB definition referencing invalid elements or operations, triggering an unhandled Go runtime panic. This panic abruptly terminates the `buildkitd` daemon process, crashing all concurrent and active build operations running on the shared host or container instance.

Red Hat's mitigation

Avoid using custom or untrusted BuildKit frontends, and restrict build submission access to verified users. Isolate build daemon instances per tenant to prevent cross-tenant build interruption.

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

Attack patterns (CAPEC)

  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

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

References

Check your stackJSON