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 the working directory's basename as a prefix can skip the filesystem entitlement check. Exploitation requires specific matching filenames next to the current project directory. Users who run untrusted Bake definitions may be affected. The issue is fixed in v0.38.1.
CVSS Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CVSS Score: 1.8
Limited-disclosure scenario: a victim runs an untrusted Bake definition and client-readable files with matching basename prefixes exist next to the project directory. This score assumes disclosure is limited to noncritical information; that limitation has not been established for all affected deployments. It does not cover exposure of credentials or other critical information, or filesystem-write impacts described in the broader report.
| Exploitability Metrics |
Vulnerable System Impact Metrics |
Subsequent System Impact Metrics |
| Attack Vector |
Local |
Confidentiality |
Low |
Confidentiality |
None |
| Attack Complexity |
Low |
Integrity |
None |
Integrity |
None |
| Attack Requirements |
Present |
Availability |
None |
Availability |
None |
| Privileges Required |
None |
| User Interaction |
Active |
Limited-disclosure scenario: a victim runs an untrusted Bake definition and client-readable files with matching basename prefixes exist next to the project directory. This score assumes disclosure is limited to noncritical information; that limitation has not been established for all affected deployments. It does not cover exposure of credentials or other critical information, or filesystem-write impacts described in the broader report.
CVSS 4.0
Run only trusted Bake definitions until upgrading. Check that Bake definitions do not contain suspicious paths outside trusted directories. The issue requires specific matching filenames next to the current project directory.
Upgrade Docker Buildx to v0.38.1 or later.