CVE-2025-0495

What it actually does

Secrets supplied directly as attribute values in cache-to or cache-from configurations are captured verbatim in OpenTelemetry trace arguments and persisted in BuildKit daemon history records.

Why it matters to the business

Build credentials or tokens may be exposed in trace data or daemon history, increasing risk of unauthorized access to build caches or dependent services; urgency is low given the absence of known exploitation and limited affected packages.

How an attack unfolds

An attacker with local access supplies cache configuration containing secrets via the CLI; the values are recorded in OpenTelemetry traces and BuildKit history where they can later be retrieved by inspecting those records.

How to fix it

Upgrade affected Chainguard packages to the fixed versions: py3.11-torchvision-cuda-11.8 to 0.18.1-r3 and py3.11-wheels-torchvision-cuda-11.8 to 0.18.1-r3. Prefer passing secrets via environment variables or registry authentication for the GitHub cache backend.

How to confirm the fix worked

Verify package versions match the fixed releases, review build configurations to ensure secrets are not supplied as inline attributes, and confirm OpenTelemetry exporters and BuildKit history do not contain test secret values after builds.

Typical attack path

1. Obtain local access to a system running Buildx with cache backends configured via attributes
2. Invoke build commands that include secret values directly in cache-to or cache-from flags
3. Access resulting OpenTelemetry traces or query BuildKit daemon history to extract the captured secrets

How to detect it

Inspect OpenTelemetry trace exports and BuildKit daemon history records for strings matching cache attribute patterns that contain credential-like values; review CLI command arguments logged during builds.

What your security team should do

• Apply the listed package upgrades immediately on all affected Chainguard images
• Audit existing build pipelines and CI configurations for inline secret attributes in cache settings
• Update build documentation to mandate environment-variable or registry-auth secret handling
• Monitor OpenTelemetry collection points and BuildKit history retention policies for sensitive data