In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition that builds multiple targets together may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, filesystem paths from some targets are not verif...
Product
debian/docker-buildx vulnerabilities
5 published CVES affecting debian/docker-buildx, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 1
- Medium
- 3
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Latest debian/docker-buildx CVEs
Newest publication first
-
MediumCVSS 5.6 EPSS 0.11%
-
LowCVSS 1.8 EPSS 0.15%
In Docker Buildx versions v0.19.0 through v0.38.0, an untrusted Bake definition may expose files accessible to the Buildx client without the expected fs.read approval. Under certain conditions, paths under the same parent directory as the current working directory whose names use...
-
HighCVSS 7.3 EPSS 0.13%
Buildx bake requires the user to grant entitlements with --allow or an interactive prompt before a build reaches outside the working directory. Under --progress=rawjson that consent step is skipped.
-
MediumCVSS 6.9 EPSS 0.29%
Docker Buildx Bake does not request the expected fs.read approval for certain filesystem inputs. An untrusted Bake definition can expose a readable file through a pathless secret whose ID is interpreted as a client-side pathname, or consume a local OCI image layout outside the pr...
-
CVE-2025-0495 Secrets leakage to telemetry endpoint via cache backend configuration via buildx
PublishedMediumCVSS 4.1 EPSS 0.20%Buildx is a Docker CLI plugin that extends build capabilities using BuildKit. Cache backends support credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. When supplied as user input, these secure values may be inadvertently captured in...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.