What happened
L3 reflects security-boundary failures in a mainstream developer tool. Neither a confirmed host takeover nor a victim count is established. The separate eMudhra trust-store response still requires attention; this release batch concerns different flaws.
The kernel flaw was already public before this Desktop release; this entry covers the October 26 Desktop remediation batch, not a newly discovered Linux bug.
What’s in the bowl
Third-party credentials logged in cleartext
Docker’s CNA identifies versions 4.39.0 to before 4.97.0. Insufficient IPC redaction exposes third-party API keys/OAuth tokens to readers of local logs or diagnostic bundles; these are not Docker account tokens.
VM network-stack corruption
A container can abuse bad IPv4 checksum metadata through TUN or AF_PACKET to corrupt the VM network stack; the notes do not establish a host escape.
Fixed versions
| Product | Safe from | Note |
|---|
| Docker Desktop | 4.97.0 | Includes existing host-log/crash-dump cleanup |
Crime-scene timeline
Oct 15, 2026
Linux publishes the underlying kernel CVE
Oct 26, 2026
Docker Desktop 4.97.0 released
Oct 27, 2026
Docker publishes the credential CVE record
Who said what
We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.