# Docker Desktop release history and what changed since 2024 Source page: https://dev-news.anonyfox.com/docker-desktop/ Every Docker Desktop release since January 2024 from Docker's release notes, and what happened to the Docker stories dev-news covered back then. ## Where it stands (2026-10-24) Docker Desktop 4.96.3 came out on 22 October 2026, the third release in two days with the same fix: Docker no longer trusts certificates from a compromised eMudhra intermediate CA. The notes for 4.96.1 and 4.96.2 say the fix "is being rolled out in batches as individual Docker Desktop components are updated", and the notes for 4.96.3 drop that line without saying the batches are done. Docker Desktop has shipped 18 releases in 2024, 32 in 2025 and 50 so far in 2026, and no month this year has had fewer than four. ## Latest stable releases - [4.96.2](https://docs.docker.com/desktop/release-notes/#4962) (2026-10-22): Removed trust for certificates issued by the compromised eMudhra intermediate CA. - [4.96.3](https://docs.docker.com/desktop/release-notes/#4963) (2026-10-22): Removed trust for certificates issued by the compromised eMudhra intermediate CA. - [4.96.1](https://docs.docker.com/desktop/release-notes/#4961) (2026-10-21): Removed trust for certificates issued by the compromised eMudhra intermediate CA. - [4.96.0](https://docs.docker.com/desktop/release-notes/#4960) (2026-10-19): Fixed an issue where the error dialog could close unexpectedly on systems under memory pressure. - [4.95.0](https://docs.docker.com/desktop/release-notes/#4950) (2026-10-12): Fixed the engine restarting right after Docker Desktop starts when an admin policy enables Enhanced Container Isolation. - [4.94.0](https://docs.docker.com/desktop/release-notes/#4940) (2026-10-05): Fixed an issue where Resource Saver could pause the VM before the Docker API was ready, causing transient errors during engine startup or restart. - [4.93.0](https://docs.docker.com/desktop/release-notes/#4930) (2026-09-28): CLI plugin updates are now managed directly from the app bundle and the Automatically update components setting has been removed. - [4.92.0](https://docs.docker.com/desktop/release-notes/#4920) (2026-09-21): Updated containerd to v2.3.5 , addressing CVE-2026-53495. - [4.91.0](https://docs.docker.com/desktop/release-notes/#4910) (2026-09-14): Fixed an issue where the Last modified column in the Volumes and container filesystem browsers displayed inaccurate timestamps like '57 years ago' instead… - [4.90.0](https://docs.docker.com/desktop/release-notes/#4900) (2026-09-07): Updated the Kind cloud provider image to v0.7.0 , addressing CVE-2026-46595 and CVE-2026-39834. - [4.89.0](https://docs.docker.com/desktop/release-notes/#4890) (2026-08-31): Fixed an issue where background container and image polling was waking the Docker engine unnecessarily when Resource Saver mode was active. - [4.88.1](https://docs.docker.com/desktop/release-notes/#4881) (2026-08-25): Fixed an issue where opening the Dashboard would incorrectly redirect unauthenticated users to the sign-in prompt page. - [4.88.0](https://docs.docker.com/desktop/release-notes/#4880) (2026-08-24): Fixed an issue where Docker Desktop reported enable fsverity failed: operation not supported as the crash cause instead of the real underlying error. - [4.87.0](https://docs.docker.com/desktop/release-notes/#4870) (2026-08-17): Fixed a bug where the in-app update failed with Source and destination path must have identical roots when Docker Desktop was installed to a custom… - [4.86.0](https://docs.docker.com/desktop/release-notes/#4860) (2026-08-10): Addressed CVE-2026-17106, a destination-escape flaw in docker container cp. ## In the dev-news log - **Docker Desktop 4.96.2 and 4.96.3** (2026-10-22). Both carry the same eMudhra distrust note as 4.96.1, for the next batch of components. Three patch releases in two days for one revoked intermediate. [log](https://dev-news.anonyfox.com/log/2026-10-22/#docker-desktop-1) - **Docker Desktop 4.96.1** (2026-10-21). Removes trust for certificates issued by the compromised eMudhra intermediate CA. Docker's notes say an attacker with network access could have used those certificates to intercept TLS from the CLI and daemon. Docker says the fix ships in batches as components are updated. [log](https://dev-news.anonyfox.com/log/2026-10-21/#docker-desktop-2) - **Docker Desktop 4.96.0** (2026-10-19). Docker networks that take addresses inside the internal 192.168.65.0/24 range are now rejected. Before this, such a network could leave Desktop stuck on "Starting the Docker Engine...". Ships Engine 29.9.1 and containerd 2.4.2. [log](https://dev-news.anonyfox.com/log/2026-10-19/#docker-desktop-3) ## What happened to the stories we covered ### Docker Desktop on Windows on Arm (2024-05-23) Original source: https://www.docker.com/blog/announcing-docker-desktop-support-for-windows-on-arm/ Arm still turns up in the fix lists: 4.81.0 on 6 July 2026 fixed a regression where Docker Desktop would not start on WSL2 kernels that could not attach its file-sharing eBPF probes, such as on Windows on Arm. ### AuthZ plugin bypass in Docker Engine (2024-07-23) Original source: https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/ Docker Desktop 4.33.0 shipped the Engine fix for CVE-2024-41110 two days later, on 25 July 2024. ### Docker Desktop 4.34 and the MSI installer (2024-09-03) Original source: https://www.docker.com/blog/docker-desktop-4-34/ The MSI installer went generally available in 4.34.0 on 29 August 2024, and it comes up again in the notes of 16 later releases, most recently 4.95.0 on 12 October 2026. Releases since 2024: 100 stable, 0 prereleases. JSON: https://dev-news.anonyfox.com/docker-desktop.json. Feed: https://dev-news.anonyfox.com/docker-desktop/feed.xml