Docker Desktop 4.97.0: patch the app and check old diagnostics
The October 26 release fixes credential logging and a VM kernel issue. Copied diagnostics can still require attention after the upgrade.
What changed
Docker Desktop 4.97.0 fixes CVE-2026-114409, which could place third-party API keys and OAuth tokens in logs or diagnostics, and CVE-2026-99999, a VM kernel network-stack issue. The OAuth tokens described are not Docker account tokens.
Why it matters
The update cleans existing host logs and crash dumps, but copies you saved or shared can remain. This advisory concerns Docker Desktop; the Docker CLI or a remote Engine version alone does not establish applicability.
What to do
- Check the Desktop application version and use Docker’s official update path to 4.97.0 or a later compatible patched release.
- Review retained or shared diagnostics from 4.96.x or earlier. Sanitize or remove exposed copies according to your incident-handling process, preserving required evidence.
- If actual live credentials were exposed, review access and plan their revocation or rotation with the issuing service; do not paste secrets into a ticket or AI prompt.
Verify the result
Verify the application build after restart and document how copied diagnostics were handled. Updating the application cannot erase a file previously sent to someone else.
Official sources
Take it into your project
Get the files, keep the guide, or give your coding assistant a ready-to-use brief.
Set it up with AI
Copy this English prompt into your coding assistant. It includes the article, available files and project setup steps.
View the setup prompt
Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/docker-desktop-4-97-logs-security-fix?lang=en
Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.
Use the article and its examples as references. Identify any missing project files before making changes.
If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.
Additional project setup instructions:
Assess Docker Desktop against the official 26 October 2026 release 4.97.0: https://docs.docker.com/security/security-announcements/ . Check the Desktop application version, not only docker --version. CVE-2026-114409 concerns third-party API keys and OAuth access tokens in local logs and diagnostics; these are not Docker-account OAuth tokens. CVE-2026-99999 is a separate VM-kernel network-stack issue. Inventory retained or shared diagnostics without printing secrets. Propose the official Desktop update and a plan to sanitize copied diagnostics. If real credentials were exposed, identify their issuing service and propose proportionate revocation or rotation with dependencies mapped first. Do not upload diagnostics, delete evidence or rotate credentials without approval. Do not assume this Desktop advisory establishes that a remote Docker Engine server is affected.
Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.
Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.Assess Docker Desktop against the official 26 October 2026 release 4.97.0: https://docs.docker.com/security/security-announcements/ . Check the Desktop application version, not only docker --version. CVE-2026-114409 concerns third-party API keys and OAuth access tokens in local logs and diagnostics; these are not Docker-account OAuth tokens. CVE-2026-99999 is a separate VM-kernel network-stack issue. Inventory retained or shared diagnostics without printing secrets. Propose the official Desktop update and a plan to sanitize copied diagnostics. If real credentials were exposed, identify their issuing service and propose proportionate revocation or rotation with dependencies mapped first. Do not upload diagnostics, delete evidence or rotate credentials without approval. Do not assume this Desktop advisory establishes that a remote Docker Engine server is affected.
Keep exploring
LLM, RAG or AI agent? Understand the differences, then build the same practical case
A detailed guide to what a model knows, what retrieval adds and how an agent uses tools. Follow one event-support request from a general answer to an evidence-backed answer and a controlled local draft, with diagrams, English prompts and a runnable project.
Build a PDF-reading RAG with n8n: an exhibitor copilot, step by step with screenshots
Create an assistant that combines an event programme, exhibitor guide and venue information into a useful arrival briefing. A complete walkthrough with real n8n screenshots, sample PDFs, importable workflows, local AI and source checks.
Triage vulnerable dependencies with AI without blindly forcing an update
Read an npm audit report, separate severity from reachability and verify one compatible change. Includes a fictional report and five tests.