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

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

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.

## Remediation

- workaround: Restrict access to existing local application logs and diagnostics bundles that may contain tokens, and delete or sanitize copies of them. (source: CNA: Docker)

## Affected products and versions

- Docker / Docker Desktop: ≥ 4.43.0; < 4.94.0 (affected, semver); 4.94.0 (unaffected, semver). Source: CNA: Docker; platforms: Linux, MacOS, Windows

## Severity and prioritization

- CVSS 4.0: 5.7 (medium); 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; source: CNA: Docker

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-532

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://docs.docker.com/desktop/release-notes/#4940 (CNA: Docker; release-notes)

## Provenance

- CNA: Docker: https://www.cve.org/CVERecord?id=CVE-2026-123082; retrieved 2026-11-10; source updated 2026-11-10

Revision: 69b516d2e8da5b0f6c438479b3bc6a7fe68a5dbad482f242b11de38a799524eb

Canonical: https://y2.dev/cve/CVE-2026-123082

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.