{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93326 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93326 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93326 and fix it if it is affected.\n\nWhat it is: CVE-2026-93326 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93326 in the wild and no public exploit code.\n\nAffected product: moby BuildKit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93326/ (Markdown: https://insights.sbomify.com/CVE-2026-93326/index.md)","id":"CVE-2026-93326","markdown":"https://insights.sbomify.com/CVE-2026-93326/index.md","name":"CVE-2026-93326","record":{"aliases":["AZL-106812","BELL-CVE-2026-93326","GHSA-66hf-6vf5-87hc","UBUNTU-CVE-2026-93326"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"BuildKit","requires_auth":"low_privilege","summary":"Attackers can bypass policy validation in BuildKit by crafting Git build sources to spoof remote URLs, undermining security controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-180","name":"Incorrect Behavior Order: Validate Before Canonicalize"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Crafted Git build source can bypass certain policy validation","id":"CVE-2026-93326","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authorization in MCP Toolbox for Databases allows Arbitrary File Read and Write","id":"CVE-2026-93328"},"packages":[],"prev":{"headline":"Oversized Dockerfile or .dockerignore can exhaust buildkitd memory","id":"CVE-2026-93323"},"products":["BuildKit"],"published":"2026-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["moby"]},"summary":"Attackers can bypass policy validation in BuildKit by crafting Git build sources to spoof remote URLs, undermining security controls.","url":"https://insights.sbomify.com/CVE-2026-93326/"}