# CVE-2025-6587: Exposure of system environment variables in Docker Desktop diagnostic logs

> Attackers with log access can read sensitive environment variables from Docker Desktop diagnostics, potentially leading to unauthorized system access.

- **Severity:** Medium 5.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-qj23-w8jm-w8wv

## What is CVE-2025-6587?

CVE-2025-6587 is a medium-severity vulnerability in Docker Desktop, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-6587?


## How do I fix CVE-2025-6587?

No fix has been published for CVE-2025-6587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6587 being exploited?

There is no known exploitation of CVE-2025-6587 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6587 and fix it if it is affected.

What it is: CVE-2025-6587 is a medium-severity vulnerability in Docker Desktop, published on 3 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6587 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6587/ (Markdown: https://insights.sbomify.com/CVE-2025-6587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6587
- OSV: https://osv.dev/vulnerability/CVE-2025-6587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6587/
Summaries are generated and may contain mistakes; the official description above is the record.