CVE-2026-114409
Docker Desktop logs can expose stored third-party credentials
Docker Desktop before version 4.97.0 could write third-party API keys and OAuth access tokens in cleartext to local application logs and diagnostics bundles due to insufficient IPC payload redaction. An attacker with read access to these files could obtain the credentials. These OAuth tokens are not Docker account tokens. Docker Desktop 4.94.0 and 4.95.0 addressed the known logging paths, but logs containing credentials can remain after upgrading. Docker Desktop 4.97.0 fixes the issue and includes cleanup of existing host logs and crash dumps.
Fixes and workarounds
Fix
Upgrade to Docker Desktop 4.97.0 or later.
Source: CNA: DockerWorkaround
Restrict access to existing local application logs and diagnostics bundles that may contain credentials, and revoke or rotate exposed credentials.
Source: CNA: DockerAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Docker Desktop Docker Platforms: Linux, MacOS, Windows |
≥ 4.39.0; < 4.97.0 (affected, semver) 4.97.0 (unaffected, semver) Other versions: unaffected |
CNA: Docker |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 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:N/SI:N/SA:N | CNA: Docker |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://docs.docker.com/desktop/release-notes/#4970CNA: Docker · release-notes
- https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#check-the-logsCNA: Docker · product
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.