Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/docker/buildx

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.1GoPublished

    buildx allows a possible credential leakage to telemetry endpoint

    CVE-2025-0495 · GHSA-m4gq-fm9h-8q75

    Affected
    • Go github.com/docker/buildx <= 0.21.2
    Fixed in
    0.21.3· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 0.21.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →