cve.bz

CVE-2026-93320 moby buildkit: Confused Deputy

6.0 mediumEPSS 0.1%

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

On this page
BuildKit may be tricked into performing file actions with special file inodes where regular files are expected. Special files may block operations or, on rootful workers, allow unintended host device access.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:H/SA:H
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; 2nd 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-441 Unintended Proxy or Intermediary (Confused Deputy)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

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

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

Red Hat's statement

A flaw was found in BuildKit's file handling subsystem during build context extraction and layer processing. BuildKit fails to restrict operations to regular files, incorrectly interacting with special file inodes such as character or block devices and FIFOs. An attacker supplying a crafted build context or Dockerfile can cause blocking I/O calls to trigger a denial of service. Furthermore, on rootful worker nodes lacking user namespace isolation, an attacker can manipulate device nodes to gain unauthorized read and write access to underlying host devices.

Red Hat's mitigation

Execute BuildKit workers in rootless mode with user namespaces enabled to prevent unauthorized host device interaction. Pre-filter and sanitize build contexts in CI/CD pipelines to reject non-regular file inodes prior to invoking the build engine.

ProductPackageStateAdvisory
Red Hat Hardened ImagesbuildahNot affected
Red Hat Hardened ImagespodmanNot affected
Red Hat Hardened ImagestrivyNot affected
Red Hat Quay 3quay/quay-builder-rhel8Not affected
Red Hat Quay 3quay/quay-builder-rhel9Not affected

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

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

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

References

Check your stackJSON