CVE-2026-123082 · Runtime
NO FIX YET
Docker Desktop before 4.94.0 wrote the signed-in user's Docker Hub access token into application logs and diagnostics bundles. Anyone who can read those files can use the token to read and modify that user's Docker Hub data while the token stays valid.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Docker Desktop before 4.94.0 who is signed in to Docker Hub. Exposure requires read access to the local logs or diagnostics bundles, and the token stays usable until it is revoked or expires. Users on managed hosting or Docker Engine alone without Docker Desktop are not described as affected.
Not affected if docker-desktop-4.94.0-or-later, not-signed-in-to-docker-hub
Who cares docker-desktop, docker-hub, macos, windows
4.94.0.Unknown from the sources.
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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.