CVSS 4.0
6.0 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NMedium (6.0) in moby buildkit. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:NExplain CVE-2026-93326 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93326?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93326?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-93326 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| moby BuildKit | through 0.33.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 26.04:LTS, 26.10, Pro:20.04:LTS and 2 more | docker.io, docker.io-app | no fix listed | UBUNTU-CVE-2026-93326 |
| Ubuntu | Pro:16.04:LTS, Pro:18.04:LTS | docker.io | no fix listed | UBUNTU-CVE-2026-93326 |
| Azure Linux | 3 | moby-engine | no fix listed | AZL-106812 |
| Alpaquita | 25 | docker | no fix listed | BELL-CVE-2026-93326 |
| Alpaquita | stream | docker | 29.9.0-r0 | BELL-CVE-2026-93326 |
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 rates this Moderate.
A flaw was found in BuildKit's Git source resolution logic when evaluating remote repository URLs. An authenticated user capable of defining build steps can craft a Git source definition that spoofs its remote URL during clone operations, bypassing source-repository policy filters. Build pipelines that enforce access control or provenance solely by repository URL may ingest untrusted source code, leading to build artifact tampering and unauthorized code execution within the build container. Stricter validation mechanisms using commit SHAs or cryptographic commit signatures remain unaffected.
Configure build pipelines and admission policies to validate Git sources using immutable commit SHAs or cryptographic commit signatures rather than repository URLs alone. Restrict build definition privileges in CI/CD pipelines to trusted contributors.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | buildah | Not affected | |
| Red Hat Hardened Images | podman | Not affected | |
| Red Hat Hardened Images | trivy | Not affected | |
| Red Hat Quay 3 | quay/quay-builder-rhel8 | Fix deferred | |
| Red Hat Quay 3 | quay/quay-builder-rhel9 | Fix 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-93326.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.