CVE-2026-93326
Severity not reportedData quality: awaiting analysis.
NVD has not completed analysis, so CVSS and affected-product data may be missing or change.
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules.
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
CVSS
—
Awaiting analysis by NVD
Timeline (UTC)
Published: 2026-10-05 21:16
Modified: 2026-10-06 15:08
NVD status: Awaiting Analysis
Last synced 3 days ago
Verified against the source API 2026-10-27 06:57 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/moby/buildkit/releases/tag/v0.33.1 security@docker.com
- https://github.com/moby/buildkit/security/advisories/GHSA-66hf-6vf5-87hc security@docker.com
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 06:57 UTC · record ↗