Secret disclosure via environment-variable diagnostic logging
Published Jul 3, 2025 · Updated Feb 26, 2026
Information exposure in Docker Desktop before 4.43.0 allows local users with log access to obtain secrets from diagnostic logs. Shell auto-completion causes system environment variables to be recorded during diagnostic-log collection instead of excluding their names and values. Exploitation requires read access to those logs; exposed API keys or passwords can enable unauthorized access to other systems.
Summary
What happened
Information exposure in Docker Desktop before 4.43.0 allows local users with log access to obtain secrets from diagnostic logs. Shell auto-completion causes system environment variables to be recorded during diagnostic-log collection instead of excluding their names and values. Exploitation requires read access to those logs; exposed API keys or passwords can enable unauthorized access to other systems.
The record
- CVE
- CVE-2025-6587
- Published
- Jul 3, 2025
- Updated
- Feb 26, 2026
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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.
- Affected versionversion=0 <4.43.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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