{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-15793 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15793 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15793 is a medium-severity command injection vulnerability in moby BuildKit, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-15793 and fix it if it is affected.\n\nWhat it is: CVE-2026-15793 is a medium-severity command injection vulnerability in moby BuildKit, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-15793 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-15793/ (Markdown: https://insights.sbomify.com/CVE-2026-15793/index.md)","id":"CVE-2026-15793","markdown":"https://insights.sbomify.com/CVE-2026-15793/index.md","name":"CVE-2026-15793","record":{"aliases":["GHSA-hw3h-2gp9-cxpv","UBUNTU-CVE-2026-15793"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"BuildKit","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands on the host by providing a malicious Git bundle when the checkout bundle feature is enabled.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[{"product":"buildkit","vendor":"mobyproject"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"BuildKit custom frontends or clients using the raw low-level API can set git.checkoutbundle=true when checking out Git sources. If the Git source is malicious, this could lead to a crafted command invocation on the host.","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":"Git source checkout from a bundle file could lead to command injection","id":"CVE-2026-15793","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Grid/List View for WooCommerce","id":"CVE-2026-15794"},"packages":[],"prev":{"headline":"Possible panic when incorrect parameters sent from frontend","id":"CVE-2026-15792"},"products":["BuildKit"],"published":"2026-07-21","related":[{"cvss_score":10,"headline":"BuildKit possible host system access from mount stub cleaner","id":"CVE-2024-23652","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":9.8,"headline":"BuildKit interactive containers API does not validate entitlements check","id":"CVE-2024-23653","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":8.7,"headline":"BuildKit possible race condition with accessing subpaths from cache mounts","id":"CVE-2024-23651","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":8.4,"headline":"BuildKit vulnerable to malicious frontend causing file escape outside of storage root","id":"CVE-2026-33747","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":8.2,"headline":"BuildKit Git URL subdir component can cause access to restricted files","id":"CVE-2026-33748","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":6.9,"headline":"Malicious client can bypass destination directory validation on local sources upload","id":"CVE-2026-15789","kev_date_added":null,"published":"2026-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-21","vendors":["moby"]},"summary":"Attackers can execute arbitrary commands on the host by providing a malicious Git bundle when the checkout bundle feature is enabled.","url":"https://insights.sbomify.com/CVE-2026-15793/"}