CVE-2026-114409

Docker Desktop logs can expose stored third-party credentials

CVE-2026-114409 is fixed in Docker Desktop on 2 platforms, first by Docker Desktop 4.97.0, released October 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.

RoutineFixed on 2 platforms

CVSS

5.7

No vendor severity

Exploitation

None reported

No vendor assessment

CISA KEV

Not listed

Not in the Known Exploited Vulnerabilities catalog

EPSS

0.0011

1st percentile

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.

Where it's fixed

Product	Fixed in	Fix	Released
Windows apps
Docker Desktop	4.97.0	Docker Desktop 4.97.0	Oct 23, 2026
macOS
Docker Desktop	4.97.0	Docker Desktop 4.97.0	Oct 23, 2026

Details

Published
October 27, 2026
Weakness
CWE-532: Insertion of Sensitive Information into Log File
Vendor advisory
https://nvd.nist.gov/vuln/detail/CVE-2026-114409

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/cve/CVE-2026-114409">CVE-2026-114409 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Is this on your machines?

Patchblox finds every install below the fixed version on Windows, macOS and Linux, and updates them through your release rings.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.