cve.bz

CVE-2026-93317 moby buildkit

5.9 mediumEPSS 0.2%

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

On this page
An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest. The resulting snapshot could be cached under that digest and reused by a later victim build, compromising build-input integrity.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:L/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-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-354 Improper Validation of Integrity Check Value
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-93317 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93317?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93317?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-93317 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 BuildKitfrom 0.28.0 before 0.33.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10, Pro:20.04:LTS and 2 moredocker.io, docker.io-appno fix listedUBUNTU-CVE-2026-93317
UbuntuPro:16.04:LTS, Pro:18.04:LTSdocker.iono fix listedUBUNTU-CVE-2026-93317

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. 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 snapshot caching mechanism when pulling container blobs from remote registries or OCI-layout sources. BuildKit fails to verify that downloaded blob data matches its advertised cryptographic digest before creating and caching the snapshot. A remote attacker controlling a registry or blob source can supply manipulated contents under a valid digest, causing BuildKit to cache poisoned layers. Subsequent builds referencing that digest reuse the tampered layer, compromising build artifact integrity.

Red Hat's mitigation

Configure BuildKit to pull images and blobs exclusively from trusted, authenticated registries. Avoid sharing build daemon cache instances across untrusted workloads and regularly prune cached snapshots.

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

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

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

References

Check your stackJSON