The vulnerability allows an attacker who has control over an untrusted Bake definition to cause Docker Buildx to expose file system paths during multi‑target builds that bypass the normal filesystem read entitlement checks. As a result, the Buildx client can read files it should not have access to, potentially leaking secrets or configuration data from the build context. This flaw represents an unauthorized file read that can lead to information disclosure or local privilege escalation within the build environment.

The issue affects Docker Buildx versions 0.19.0 through 0.38.0. Customers using any of those releases with untrusted Bake files for multi‑target builds are at risk. The fix is implemented in 0.38.1. Docker Buildx is part of the Docker Engine tooling for building multi‑platform images and is commonly used in CI/CD pipelines.

The CVSS score of 5.6 indicates a moderate severity, and the EPSS score is currently unavailable. The vulnerability is not listed in CISA’s KEV catalog. Attackers can exploit the flaw by supplying a crafted Bake definition that references forbidden paths; local users with the ability to invoke Buildx can trigger the bypass, meaning the attack vector is local. A successful exploitation would allow reading any file reachable under the Buildx process, compromising confidentiality of build artifacts and possibly revealing credentials stored in the build context.