github.com/docker/buildx
Affected
- introduced
0, fixed0.21.3(semver)
Fixed versions
0.21.3
Fix
- Fixed version
0.21.3go get github.com/docker/[email protected]
Advisory
Also known as: CVE-2025-0495, GO-2025-3527
buildx allows a possible credential leakage to telemetry endpoint
Impact
Some cache backends allow configuring their credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. If this was done by the user, these secure values could be captured together with OpenTelemetry trace as part of the arguments and flags for the traced CLI command. Passing tokens to Github cache backend via environment variables or using registry authentication is not affected.
If you passed a token value like this and use a custom OpenTelemetry collector for computing traces you should make sure that your traces are kept secure. OpenTelemetry traces are also saved in BuildKit daemon's history records.
Patches
Issue has been fixed in Buildx v0.21.3 or newer.
Workarounds
Avoid passing cache backend credentials with CLI arguments. Make sure access to traces and BuildKit history records is kept secure.
Medium Basis: The source's own band: MODERATE
0, fixed 0.21.3 (semver)0.21.3
0.21.3go get github.com/docker/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0