Quick answers
- Is CVE-2026-123082 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123082 being exploited in the wild.
- How severe is CVE-2026-123082?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Docker Desktop before 4.94.0.
- Is there a fix for CVE-2026-123082?
- Yes: fixed in Docker Desktop 4.94.0. Until then: After upgrading to Docker Desktop 4.94.0, review and delete log files and diagnostics bundles from earlier versions that may contain exposed tokens. Consider rotating Docker Hub access tokens if diagnostic bundles were shared or log files were accessible to untrusted parties. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123082 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-123082?
- Check whether you run Docker Desktop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Docker Desktop 4.94.0
After upgrading to Docker Desktop 4.94.0, review and delete log files and diagnostics bundles from earlier versions that may contain exposed tokens. Consider rotating Docker Hub access tokens if diagnostic bundles were shared or log files were accessible to untrusted parties.
Technical details
Docker Desktop failed to redact IPC payloads that were bare JSON strings or arrays before logging, and a component logged Docker Hub access tokens (JWTs) when requesting them from the backend. An attacker with read access to application logs or diagnostics bundles can extract the token and use it to authenticate to Docker Hub as that user. Docker Desktop 4.94.0 adds redaction, but does not rewrite existing logs that may contain tokens.
Affected products
- Docker Desktop before 4.94.0
Timeline
- 2026-11-10: disclosed