{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-114409 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-114409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114409 is a medium-severity vulnerability in Docker Desktop, published on 27 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114409 and fix it if it is affected.\n\nWhat it is: CVE-2026-114409 is a medium-severity vulnerability in Docker Desktop, published on 27 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-114409 in the wild and no public exploit code.\n\nAffected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-114409/ (Markdown: https://insights.sbomify.com/CVE-2026-114409/index.md)","id":"CVE-2026-114409","markdown":"https://insights.sbomify.com/CVE-2026-114409/index.md","name":"CVE-2026-114409","record":{"aliases":["GHSA-vqw9-m2fj-xfwx"],"analysis":null,"analysis_generated_by":null,"assigner":"Docker","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Docker Desktop logs can expose stored third-party credentials","id":"CVE-2026-114409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"WP VR 8.5.49 - 9.0.2 - Contributor+ Stored XSS via Hotspot Content","id":"CVE-2026-114429"},"packages":[],"prev":{"headline":"e107 CMS before 2.3.13 Reflected XSS via search.php author Parameter","id":"CVE-2026-114407"},"products":["Docker Desktop"],"published":"2026-10-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-27","vendors":["Docker"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114409/"}