Docker Desktop
CVE-2025-13743
LOW
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local access to host or exported bundle
-
ExploitUser generates diagnostics after Hub errors
-
ExecutionExpired PATs serialized into log output
-
ImpactRead sensitive tokens from bundle
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Log data sanitization
|
| Exploitation Conditions | Exploitation requires: (1) the affected workflow actually occurring - a user must trigger Hub 'access denied' (or similar) errors and then generate/export a Docker Desktop diagnostics bundle (the UI:P / user-interaction condition); (2) local or post-export access to that diagnostics bundle on the host or wherever it was shared (AV:L, PR:L - the actor needs at least low-privileged local account access to reach the generated file). Strong limiting factors: the exposed Hub PATs are EXPIRED and therefore of little authentication value; no integrity or availability impact; and exploitation is confined to the specific diagnostics-export code path rather than any default network-facing surface. There is no remote or unauthenticated path. |
| Impact | This is a genuinely low-priority issue, and the signals are consistent rather than conflicting. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N) scores only 2.4, reflecting a local attack vector, required low-level privileges, passive user interaction, and merely Low confidentiality impact with no integrity or availability effect. EPSS corroborates this at 0.21% (11th percentile), indicating very low probability of exploitation activity. The vulnerability is NOT in CISA KEV and no public proof-of-concept is referenced, so there is no evidence of active exploitation. Critically, the leaked Hub Personal Access Tokens are described as EXPIRED, which sharply reduces the practical value of any disclosure - an attacker recovering them generally cannot use them for authentication. The only reportedly confirmed fact is the vendor's own disclosure (reported by security@docker.com); there is no independent patch-version confirmation in the provided data. Net: a real but minor information-hygiene defect, not an operational priority. |
| Exploit ScenarioDerived | A developer running Docker Desktop encounters Hub 'access denied' errors and generates a diagnostics bundle for support; the bundle's serialized error objects embed expired Hub PATs in the log output. An attacker who later obtains that exported bundle (e.g., from a shared support ticket, file share, or local disk) can read the tokens, though their expired status limits real-world abuse. No public exploit code is referenced and this requires local access to the generated diagnostics artifact. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Export of Docker Desktop diagnostics bundles can leak expired Hub personal access tokens (PATs) when Hub access-denied errors are serialized into log output. The affected surface is Docker Desktop as a whole, reflected by the wildcard CPE cpe:2.3:a:docker:docker_desktop:*:*:*:*:*:*:*:*, so all versions are potentially in scope until a fixed release is identified. A low-privileged local actor who can reach an exported bundle after a user triggers an access-denied error and generates diagnostics can recover the expired token; the vendor score is 2.4 and the independent local assessment is CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N, with EPSS at 0.21 percent (11th percentile), no public exploit identified at time of analysis, and no CISA KEV listing. Because the exposed PATs are expired, real authentication value is minimal and the practical risk is secret-hygiene and information-disclosure rather than account compromise.
RemediationAI
The provided data does not identify an exact fixed Docker Desktop version, so patch availability is not confirmed from available sources; check the Docker Desktop release notes and the advisory at https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#troubleshoot-menu for a version that redacts credential fields from serialized error objects, and upgrade as soon as a specific fixed release is named. Until then, treat every exported diagnostics bundle as sensitive: avoid generating and exporting diagnostics while Hub access-denied errors are present, and if a bundle must be produced, restrict its filesystem permissions and review it before sharing. Rotate or revoke all Docker Hub PATs regardless of expiry, since expired tokens are low value but their appearance confirms the serialization flaw and any newly issued tokens could be exposed by the same code path. As compensating controls, limit local account access to hosts that generate diagnostics bundles (reduces the AV:L and PR:L prerequisites) and disable or tightly control automated diagnostics collection, accepting that this reduces supportability and can slow troubleshooting. Apply network and disk controls around shared support artifacts so bundles are not broadly readable, with the trade-off that such controls add handling overhead and may not stop an actor who already holds local read access.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-532, insertion of sensitive information into a log file, occurring specifically in Docker Desktop's diagnostics-bundle generation path. When a Hub operation returns an access-denied or similar error, Docker Desktop serializes the error object into diagnostic log output without redacting credential fields, so a Hub personal access token embedded in that error context is written into the bundle. Diagnostics bundles are troubleshooting archives that users deliberately generate and often share with support or attach to issues, which is why the leak becomes meaningful only after export and distribution. The CPE is a wildcard for docker:docker_desktop, meaning no specific fixed version is encoded in the available data; the Exploitation conditions assessed independently require the access-denied workflow to actually occur, a user to generate and export the bundle (the UI:R condition), and a local actor to gain read access to the resulting file (AV:L, PR:L). The tokens involved are expired, and the assessment records no integrity or availability impact and no remote or unauthenticated path.
Know when Docker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Local access to a user-generated diagnostics bundle (AV:L, UI:R, PR:L); only low confidentiality impact from expired tokens, with no integrity or availability effect.
Primary rating from Vendor (docker).
CVSS VectorVendor: docker
DescriptionCVE.org
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.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
GitHub PoC
Exploit-DB