{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93317 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93317 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93317 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-93317 and fix it if it is affected.\n\nWhat it is: CVE-2026-93317 is a medium-severity vulnerability in moby BuildKit, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-93317 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-93317/ (Markdown: https://insights.sbomify.com/CVE-2026-93317/index.md)","id":"CVE-2026-93317","markdown":"https://insights.sbomify.com/CVE-2026-93317/index.md","name":"CVE-2026-93317","record":{"aliases":["GHSA-p3rc-w3hc-pqvv","UBUNTU-CVE-2026-93317"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"BuildKit container builder","requires_auth":"none","summary":"An attacker can poison the container blob cache with unverified content, compromising build integrity for subsequent users.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"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.","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":"Container blob cache can accept unverified content","id":"CVE-2026-93317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cache poisoning via unvalidated image layer DiffIDs","id":"CVE-2026-93318"},"packages":[],"prev":{"headline":"Starting daemon with --cdi-disabled flag can lead to panic on specific builds","id":"CVE-2026-93316"},"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":"An attacker can poison the container blob cache with unverified content, compromising build integrity for subsequent users.","url":"https://insights.sbomify.com/CVE-2026-93317/"}