dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-6587

MEDIUM · 5.2 CVSS v4.0 Published 2025-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
System environment variables are recorded in Docker Desktop diagnostic logs, when using shell auto-completion. This leads to unintentional disclosure of sensitive information such as api keys, passwords, etc.  A malicious actor with read access to these logs could obtain secrets and further use them to gain unauthorized access to other systems. Starting with version 4.43.0 Docker Desktop no longer logs system environment variables as part of diagnostics log collection.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Docker Desktop versions prior to 4.43.0 recorded system environment variables in diagnostic logs during shell auto-completion, inadvertently capturing sensitive data such as API keys and passwords. An attacker with read access to these logs could retrieve exposed credentials and pivot to other systems.

MitigationUpgrade Docker Desktop to version 4.43.0 or later, which disables logging of system environment variables in diagnostics. Audit historical logs for any exposed secrets and rotate compromised credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Docker Desktop version
    Run 'docker --version' or open Docker Desktop and go to About Docker Desktop to see the version number
    Affected if Version is earlier than 4.43.0 (e.g., 4.42.0, 4.40.0, etc.)
  2. Locate Docker diagnostic logs
    On Windows: %APPDATA%\Docker\logs\, on Mac: ~/Library/Logs/Docker/. Look for files named 'diagnostic' or 'daemon' with .log extension
    Affected if Diagnostic log files exist in the default Docker logs directory
  3. Inspect logs for environment variable exposure
    Open the most recent diagnostic log file and search for lines containing 'env', 'export', or variable assignments like 'KEY=value'. Look for patterns matching API keys, tokens, or passwords
    Affected if Log entries contain system environment variable names or their values (e.g., AWS_ACCESS_KEY_ID, password strings)
  4. Check if shell auto-completion is enabled
    Run 'docker completion --help' or check if completion scripts exist in /etc/bash_completion.d/ or ~/.docker/
    Affected if Docker shell auto-completion is installed and enabled on the host system

User is affected if running Docker Desktop version below 4.43.0 AND diagnostic logs exist that may contain environment variables from shell auto-completion sessions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Docker Desktop to version 4.43.0 or later, which disables logging of system environment variables in diagnostics. Audit historical logs for any exposed secrets and rotate compromised credentials.

Recommended fix High confidence

Docker Desktop 4.43.0 or later

  1. Open Docker Desktop on your machine
  2. Click on the Docker Desktop menu (gear icon)
  3. Navigate to the 'Check for updates' option
  4. If an update is available, download and install Docker Desktop version 4.43.0 or later
  5. After installation, restart Docker Desktop
  6. Verify the update by checking Help > About Docker Desktop to confirm version 4.43.0 or newer is installed
  7. Ensure diagnostic logs no longer contain system environment variables by generating a new diagnostic log and inspecting it

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data