CVE-2025-0495

Credential disclosure via unredacted command arguments

Published Mar 17, 2025 · Updated Mar 18, 2025

Sensitive information exposure in Docker Buildx 0.21.2 and earlier allows local users to read cache credentials from build traces. TraceCurrentCommand passed the complete process argument vector from os.Args into the OpenTelemetry command attribute, preserving cache-to and cache-from credential values. Exposure requires a user to supply credentials as cache backend attributes and an attacker to access a custom telemetry collector or BuildKit history; environment-based GitHub cache tokens and registry authentication are unaffected.

CVSS severity4.1
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive information exposure in Docker Buildx 0.21.2 and earlier allows local users to read cache credentials from build traces. TraceCurrentCommand passed the complete process argument vector from os.Args into the OpenTelemetry command attribute, preserving cache-to and cache-from credential values. Exposure requires a user to supply credentials as cache backend attributes and an attacker to access a custom telemetry collector or BuildKit history; environment-based GitHub cache tokens and registry authentication are unaffected.

The record

CVE
CVE-2025-0495
Published
Mar 17, 2025
Updated
Mar 18, 2025
Vendor
Docker
Product
Docker Buildx
Classifications
CWE-532, T1552.001
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 17, 2025CVE publishedPublication date reported by the CVE source.
  2. Mar 18, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=0.21.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Docker · Docker Buildxversion=0 <=0.21.2

Published CVSS scores

4.1Docker Inc.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo