Expired Hub PAT disclosure via serialized error logs
Published Dec 9, 2025 · Updated Dec 10, 2025
Sensitive-data exposure in Docker Desktop 4.51.0 through 4.53.0 allows local users to read expired Hub PATs from exported diagnostics. Error-object serialization writes expired authorization tokens into diagnostic log output, particularly when access-denied errors occur. Exposure requires access to a generated bundle, and the reported consequence is limited to disclosure of expired credentials.
Summary
What happened
Sensitive-data exposure in Docker Desktop 4.51.0 through 4.53.0 allows local users to read expired Hub PATs from exported diagnostics. Error-object serialization writes expired authorization tokens into diagnostic log output, particularly when access-denied errors occur. Exposure requires access to a generated bundle, and the reported consequence is limited to disclosure of expired credentials.
The record
- CVE
- CVE-2025-13743
- Published
- Dec 9, 2025
- Updated
- Dec 10, 2025
- Vendor
- Docker
- Product
- Docker Desktop
- Classifications
- CWE-532, CAPEC-155, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 2025Record 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=4.51.0 <4.54.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