{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93319 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93319 and fix it if it is affected.\n\nWhat it is: CVE-2026-93319 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93319 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-93319/ (Markdown: https://insights.sbomify.com/CVE-2026-93319/index.md)","id":"CVE-2026-93319","markdown":"https://insights.sbomify.com/CVE-2026-93319/index.md","name":"CVE-2026-93319","record":{"aliases":["AZL-106809","GHSA-4hgw-qrhw-fhg8","UBUNTU-CVE-2026-93319"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BuildKit container builder","requires_auth":"low_privilege","summary":"A malicious BuildKit frontend can trigger a data race causing the daemon to panic, resulting in denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-567","name":"Unsynchronized Access to Shared Data in a Multithreaded Context"}],"description":"A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"A malicious frontend can cause a daemon panic","id":"CVE-2026-93319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"BuildKit improperly handles special files in build snapshots","id":"CVE-2026-93320"},"packages":[],"prev":{"headline":"Cache poisoning via unvalidated image layer DiffIDs","id":"CVE-2026-93318"},"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-05","vendors":["moby"]},"summary":"A malicious BuildKit frontend can trigger a data race causing the daemon to panic, resulting in denial of service.","url":"https://insights.sbomify.com/CVE-2026-93319/"}