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-13743: CWE-532 Insertion of Sensitive Information into Log File in Docker Docker Desktop

0
Low
VulnerabilityCVE-2025-13743cvecve-2025-13743cwe-532
Published: Tue Dec 09 2025 (12/09/2025, 20:39:52 UTC)
Source: CVE Database V5
Vendor/Project: Docker
Product: Docker Desktop

Description

Docker Desktop diagnostics bundles were found to include expired Hub PATs in log output due to error object serialization. This poses a risk of leaking sensitive information in exported diagnostics, especially when access denied errors occurred.

AI-Powered Analysis

AILast updated: 12/16/2025, 21:03:15 UTC

Technical Analysis

CVE-2025-13743 identifies a vulnerability in Docker Desktop version 4.51.0 related to the improper handling of sensitive information during diagnostic data collection. Specifically, expired Docker Hub Personal Access Tokens (PATs) are included in diagnostic bundles due to error object serialization when access denied errors occur. This behavior results in the insertion of sensitive information into log files (CWE-532), which can be exported and potentially accessed by unauthorized users. Although the tokens are expired and thus less useful for direct authentication, their exposure still represents a confidentiality risk, especially if logs are shared externally or stored insecurely. The vulnerability requires local access with limited privileges and user interaction to trigger the diagnostic generation, limiting remote exploitation. The CVSS 4.0 score of 2.4 reflects low severity, emphasizing limited impact and exploitation complexity. No patches or known exploits are currently reported, but the issue highlights the need for secure handling of sensitive data in diagnostic processes. Docker Desktop is widely used in development and production environments, making this a relevant concern for organizations relying on containerization. The vulnerability does not affect integrity or availability but compromises confidentiality by leaking sensitive tokens in logs.

Potential Impact

For European organizations, the primary impact of CVE-2025-13743 is the potential leakage of sensitive authentication tokens within diagnostic logs, which could be inadvertently shared or accessed by unauthorized personnel. While the tokens are expired, their presence in logs may facilitate reconnaissance or social engineering attacks, or reveal internal infrastructure details. Organizations with strict data protection regulations, such as GDPR, may face compliance risks if sensitive information is exposed. The vulnerability is less likely to cause direct operational disruption or data integrity issues but could undermine trust in container security practices. Given Docker Desktop's popularity among developers and IT teams across Europe, especially in countries with advanced cloud and container adoption, this vulnerability could affect a broad range of sectors including finance, healthcare, and technology. The risk is heightened in environments where diagnostic bundles are routinely shared with external support or stored in less secure locations. However, the requirement for local access and user interaction limits the threat to insider or targeted scenarios rather than widespread remote exploitation.

Mitigation Recommendations

To mitigate CVE-2025-13743, organizations should implement strict access controls on diagnostic bundles generated by Docker Desktop, ensuring only authorized personnel can view or export these logs. It is advisable to avoid sharing diagnostic data externally unless it has been sanitized to remove sensitive tokens. Monitoring and auditing diagnostic data exports can help detect inadvertent leaks. Organizations should upgrade Docker Desktop to versions where this vulnerability is addressed once patches become available. In the interim, disabling or limiting diagnostic data collection in sensitive environments can reduce exposure. Developers and IT staff should be trained to recognize the risks of including sensitive information in logs and adopt secure logging practices, such as redacting tokens before serialization. Additionally, rotating Personal Access Tokens regularly and minimizing their permissions can reduce the impact if tokens are exposed. Implementing endpoint security controls to restrict local access and user privileges further reduces the risk of exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Docker
Date Reserved
2025-11-26T14:07:43.047Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 693889e152fe50f9a4851f94

Added to database: 12/9/2025, 8:43:13 PM

Last enriched: 12/16/2025, 9:03:15 PM

Last updated: 2/6/2026, 9:27:42 PM

Views: 219

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats