Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-6587: CWE-532 Insertion of Sensitive Information into Log File in Docker Docker Desktop

0
Medium
VulnerabilityCVE-2025-6587cvecve-2025-6587cwe-532
Published: Thu Jul 03 2025 (07/03/2025, 10:03:27 UTC)
Source: CVE Database V5
Vendor/Project: Docker
Product: Docker Desktop

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 22:00:57 UTC

Technical Analysis

CVE-2025-6587 is a vulnerability classified under CWE-532, which involves the insertion of sensitive information into log files. In Docker Desktop versions prior to 4.43.0, when users utilize shell auto-completion features, system environment variables are inadvertently recorded in diagnostic log files. These environment variables often contain sensitive data such as API keys, passwords, tokens, or other credentials. Because diagnostic logs are typically accessible to users with certain privileges, a malicious actor who gains read access to these logs can extract these secrets. This can lead to unauthorized access to other systems or services that rely on these credentials. The vulnerability requires local or limited privilege access (AV:L - local attack vector) and low attack complexity (AC:L), with privileges required (PR:L) but no user interaction (UI:N). The scope is high (SC:H) and the impact on confidentiality, integrity, and availability is also high (SI:H, CI:H, AI:H). Docker addressed this vulnerability starting with version 4.43.0 by ceasing the logging of system environment variables in diagnostic logs. No public exploits have been reported to date, but the risk remains significant due to the sensitivity of the leaked information.

Potential Impact

The primary impact of CVE-2025-6587 is the potential exposure of sensitive credentials and secrets stored in environment variables. If an attacker obtains these secrets, they can leverage them to gain unauthorized access to cloud services, internal APIs, databases, or other critical infrastructure components. This can lead to data breaches, privilege escalation, lateral movement within networks, and disruption of services. Organizations relying heavily on Docker Desktop for development or operational workflows may inadvertently expose secrets if diagnostic logs are not properly secured. The vulnerability also undermines trust in the security hygiene of containerized environments and could lead to compliance violations if sensitive data is leaked. Since exploitation requires access to logs, the risk is higher in environments where multiple users share systems or where log files are not adequately protected. The medium CVSS score reflects the balance between the sensitivity of leaked data and the requirement for some level of access to the system.

Mitigation Recommendations

To mitigate CVE-2025-6587, organizations should immediately upgrade Docker Desktop to version 4.43.0 or later, where the logging of environment variables in diagnostic logs has been disabled. Additionally, restrict access to diagnostic logs to only trusted administrators and users with a legitimate need, using strict file permissions and access controls. Implement monitoring and alerting for unusual access patterns to log files. Review and rotate any secrets or credentials that may have been exposed through logs prior to patching. Encourage developers and operators to avoid placing highly sensitive information in environment variables when possible, or use secret management tools that do not expose secrets in environment variables. Finally, audit and sanitize logs regularly to ensure no sensitive data is inadvertently recorded.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Docker
Date Reserved
2025-06-24T20:47:44.847Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 686656db6f40f0eb7296200d

Added to database: 7/3/2025, 10:09:31 AM

Last enriched: 2/26/2026, 10:00:57 PM

Last updated: 3/22/2026, 5:40:27 PM

Views: 380

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses