# CVE-2026-123082: Docker Desktop logs can expose the Docker Hub access token


- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-hrf4-3f42-8mh7

## What is CVE-2026-123082?

CVE-2026-123082 is a medium-severity vulnerability in Docker Desktop, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-123082?


## How do I fix CVE-2026-123082?

No fix has been published for CVE-2026-123082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123082 being exploited?

There is no known exploitation of CVE-2026-123082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123082 and fix it if it is affected.

What it is: CVE-2026-123082 is a medium-severity vulnerability in Docker Desktop, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123082 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123082/ (Markdown: https://insights.sbomify.com/CVE-2026-123082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123082
- OSV: https://osv.dev/vulnerability/CVE-2026-123082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123082/
Summaries are generated and may contain mistakes; the official description above is the record.