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.
Published: 2026-07-21
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

BuildKit’s low‑level API can set git.checkoutbundle=true when checking out Git sources. An attacker able to supply a malicious Git bundle can have that bundle’s checkout sequence execute crafted host commands, which is a classic command‑injection flaw classified as CWE‑88. The consequence is full host compromise, allowing attackers to read or modify files, install additional malware, or exfiltrate data.

Affected Systems

The flaw affects BuildKit, the build engine used by Docker. Any BuildKit instance that employs a custom frontend or directly uses the raw API with git.checkoutbundle enabled is vulnerable. No specific version range is disclosed, so all BuildKit releases lacking the patch are potentially vulnerable.

Risk and Exploitability

The CVSS score is 6.5, indicating moderate severity, yet the impact of command injection is high. < 1%, indicating current exploitation probability is very low. The vulnerability is not listed in the CISA KEV catalog. malicious Git source and either use a custom frontend or invoke the raw API; the likely attack vector would involve a BuildKit coordinator or a privileged user with the ability to configure pipelines or provide source bundles. Remote unauthenticated exploitation is unlikely unless the BuildKit service is exposed to untrusted networks.

Generated by OpenCVE AI on July 30, 2026 at 17:08 UTC.

Remediation

Vendor Workaround

The issue requires using a custom frontend together with a malicious Git source. Current Dockerfile builds are not affected.


OpenCVE Recommended Actions

  • Upgrade that includes the command‑injection fix.
  • Disallow or remove the git.checkoutbundle flag for custom frontends; use only trusted source repositories.
  • Apply the CNA‑provided workaround: avoid using git.checkoutbundle in custom frontends or the raw API with untrusted Git sources, noting that current Dockerfile builds are not affected.

Generated by OpenCVE AI on July 30, 2026 at 17:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 21 Jul 2026 23:15:00 +0000

Type Values Removed Values Added
First Time appeared Moby
Moby buildkit
Vendors & Products Moby
Moby buildkit

Tue, 21 Jul 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 21 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title Git source checkout from a bundle file could lead to command injection
Weaknesses CWE-88
References
Metrics cvssV4_0

{'score': 6.5, '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Docker

Published:

Updated: 2026-07-21T16:58:40.200Z

Reserved: 2026-07-14T19:31:45.116Z

Link: CVE-2026-15793

cve-icon Vulnrichment

Updated: 2026-07-21T16:58:31.222Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T17:15:12Z

Weaknesses
  • CWE-88

    Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')