{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93318 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93318 is a high-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-93318 and fix it if it is affected.\n\nWhat it is: CVE-2026-93318 is a high-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-93318 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-93318/ (Markdown: https://insights.sbomify.com/CVE-2026-93318/index.md)","id":"CVE-2026-93318","markdown":"https://insights.sbomify.com/CVE-2026-93318/index.md","name":"CVE-2026-93318","record":{"aliases":["AZL-106818","GHSA-f2v9-hprr-32q3","UBUNTU-CVE-2026-93318"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"BuildKit container builder","requires_auth":"none","summary":"Attackers can poison BuildKit cache with malicious layers, leading to arbitrary code execution and secret theft during subsequent builds.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"A malicious image can advertise DiffIDs from another image while containing different layer contents. In affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without validating that they matched the actual layer contents.\n\nIf a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build using the victim image may mount the attacker-controlled layer contents as the base image. This can allow code from the malicious image to run in the victim build, for example by replacing a commonly executed path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access other build resources, alter output artifacts, or hang the build.\n\nThe issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz.","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":"Cache poisoning via unvalidated image layer DiffIDs","id":"CVE-2026-93318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"A malicious frontend can cause a daemon panic","id":"CVE-2026-93319"},"packages":[],"prev":{"headline":"Container blob cache can accept unverified content","id":"CVE-2026-93317"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["moby"]},"summary":"Attackers can poison BuildKit cache with malicious layers, leading to arbitrary code execution and secret theft during subsequent builds.","url":"https://insights.sbomify.com/CVE-2026-93318/"}