buildx allows a possible credential leakage to telemetry endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

4.1 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N · score source

EPSS

• CVE-2025-0495: 0.20% estimated exploitation activity in the next 30 days; percentile 9.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

17 Mar 2025, 21:27 UTC

Last modified by the source

17 Mar 2025, 21:51 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m4gq-fm9h-8q75

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-0495

Advisory: buildx allows a possible credential leakage to telemetry endpoint
IDs: CVE-2025-0495, GHSA-m4gq-fm9h-8q75
Record: https://patchnext.com/advisories/cve-2025-0495 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/docker/buildx 0.21.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/docker/buildx: affected <= 0.21.2; fixed in 0.21.3

## Suggested inspection (read-only)
- Go github.com/docker/buildx: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/docker/buildx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m4gq-fm9h-8q75 (GitHub-reviewed advisory GHSA-m4gq-fm9h-8q75 lists affected ranges: Go github.com/docker/buildx >=0 <=0.21.2)

Commands are suggestions: review each one before running it.