Docker Desktop CVE-2026-114409

Exploitation requires that the victim has actually used third-party API keys or OAuth access tokens through Docker Desktop so that those credentials were written in cleartext to local application logs, crash dumps, or a diagnostics bundle (this conditional presence of secrets is the AT:P attack requirement). The attacker must then have local read access to those files (PR:L, AV:L) - e.g. a lower-privileged co-user, access to a backup, or receipt of a shared diagnostics bundle. Limiting factors: it is local only with no remote or network vector, no user interaction, and yields only confidentiality of third-party credentials (not Docker account tokens, and no integrity or availability impact). Note that upgrading only to 4.94.0 or 4.95.0 does not clear previously logged credentials; 4.97.0 is required for cleanup.

This is a genuine but modest-priority issue, best characterized as a high-CVSS-equivalent-on-confidentiality-only flaw whose real-world risk is tempered by its local attack surface. The supplied CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:L/UI:N, VC:H with VI:N/VA:N) scores 5.7 (Medium): exploitation is local, requires some existing privilege (PR:L) and depends on a precondition (AT:P), and the impact is confined to confidentiality of third-party credentials - notably NOT Docker account tokens, per the vendor. No EPSS score, no CISA KEV listing, and no public PoC/exploit reference are present in the input, so there is no public exploit identified at time of analysis and no signal of active or probable near-term exploitation; the vuln.today decision label is 'this_month', consistent with a patch-on-normal-cadence item rather than an emergency. The practical risk is secondary exposure: the vulnerability does not itself grant access but leaks already-used API keys and OAuth tokens into logs and diagnostics bundles, so impact depends entirely on an attacker already having read access to those local files (another local user, a backup/log-aggregation pipeline, or a diagnostics bundle shared with support/third parties). One important nuance to flag explicitly: Docker Desktop 4.94.0 and 4.95.0 only addressed the known logging paths and residual credential-bearing logs can survive an upgrade - only 4.97.0 performs cleanup of existing host logs and crash dumps, so merely upgrading to an intermediate version does not eliminate exposure. The input's 'Denial Of Service' tag conflicts with the actual CWE-532 information-disclosure nature and the VI:N/VA:N vector and should be disregarded.

On a shared or compromised workstation, an attacker with read access to a developer's local Docker Desktop log directory or an exported diagnostics bundle opens the cleartext files and harvests third-party API keys and OAuth access tokens that Docker Desktop failed to redact from IPC payloads. Because diagnostics bundles are routinely attached to support tickets or shared internally, the same credentials can leak to anyone who receives such a bundle. No public exploit is identified at time of analysis; exploitation is simple file reading and requires no special tooling once access to the files exists.