# CVE-2026-114409: Docker Desktop logs can expose stored third-party credentials


- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-vqw9-m2fj-xfwx

## What is CVE-2026-114409?

CVE-2026-114409 is a medium-severity vulnerability in Docker Desktop, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-114409?


## How do I fix CVE-2026-114409?

No fix has been published for CVE-2026-114409 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114409 being exploited?

There is no known exploitation of CVE-2026-114409 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114409 and fix it if it is affected.

What it is: CVE-2026-114409 is a medium-severity vulnerability in Docker Desktop, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114409 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114409/ (Markdown: https://insights.sbomify.com/CVE-2026-114409/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114409
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114409
- OSV: https://osv.dev/vulnerability/CVE-2026-114409

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114409/
Summaries are generated and may contain mistakes; the official description above is the record.