CVSS 4.0
5.7 mediumCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:NCVE-2026-123082
Medium (5.7) in docker docker desktop.
Docker Desktop before version 4.94.0 could write the signed-in user's Docker Hub access token (a JWT) in cleartext to application logs and diagnostics bundles. IPC payloads that were bare JSON strings or arrays were not redacted before logging, and a Docker Desktop component logged the token when it requested it from the backend. An attacker with read access to these files could obtain the token and use it to read and modify the user's Docker Hub data as that user while the token remains valid. Docker Desktop 4.94.0 redacts these payloads. The fix does not rewrite logs written by earlier versions, which can still contain tokens after upgrading.
Severity
- CWE
- CWE-532 Insertion of Sensitive Information into Log File
- OWASP Top 10
- A09:2025 Logging & Alerting Failures
- Published
- Assigned by
- Docker (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123082 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123082?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123082?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123082 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
- docker:docker desktop
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Docker Desktop | from 4.43.0 before 4.94.0 |
Attack patterns (CAPEC)
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.