NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-0495: buildx allows a possible credential leakage to telemetry endpoint

mediumCVSS 4.0 4.1GHSA-m4gq-fm9h-8q75

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.

Published Mar 17, 2025

Affected packages

github.com/docker/buildx

Ecosystem
Go
Affected
<= 0.21.2
Fixed in
0.21.3
Check
go list -m github.com/docker/buildx

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to jstawinski.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology