Docker Engine 29.9.3
I upgraded so you don't have to
Docker Engine 29.9.3 landed on November 3, 2026, and unlike most point releases in the 29 line this one is almost entirely security work. Six CVEs, a SwarmKit update, and a BuildKit bump to v0.34.2. There is one genuinely interesting bug fix on top, and one caveat that will bite anyone running Swarm behind firewalld. Verdict up front: upgrade, especially if you run Swarm or expose the BuildKit control API to anything shared.
What the upgrade fixes
- CVE-2026-116587 (GHSA-mgcc-cww5-fp2q): possible excessive CPU usage when parsing crafted RSA keys.
- CVE-2026-116591 (GHSA-fpmh-frq8-7rj8): possible panic when decompressing zstd data. A daemon panic is a denial of service for every container on the host, so this is the one I cared about most on shared build machines.
- CVE-2026-115538 (GHSA-6jhp-7446-hf7f): missing encryption and spoofing protections for Swarm overlay networks after firewalld flushes Docker's iptables rules.
- CVE-2026-115539 (GHSA-628g-hv7f-pgjc): fixed in the bundled SwarmKit update. An attacker holding a valid worker-node TLS certificate and key could obtain a manager-node certificate shortly after a Swarm leader change.
The BuildKit v0.34.2 update covers two more. GHSA-2fqp-xg6f-v7gj describes a build that resolved metadata for the same Git source reference twice and could crash the daemon through resolver cache poisoning. GHSA-w26x-xg27-7qjc covers a malicious client with access to the BuildKit control APIs setting extended attributes on files outside the BuildKit state directory, which can hand elevated privileges to host programs. If your build service is reachable by more than one team, this is the reason to move quickly.
The overlay network problem
The firewalld issue deserves its own paragraph because the fix is a package upgrade, not a config change you can apply on your own. When firewalld reloads, it flushes the iptables rules Docker installed, and on 29.9.2 and earlier the overlay network lost both encryption and spoofing protections silently. Nothing announced itself. Traffic kept flowing. If you run Swarm behind firewalld and reload rules on a schedule, check your audit trail: you may have been running unprotected for longer than you think. After upgrading, verify that overlay encryption is actually in place rather than assuming the reload problem disappeared.
Also in this release
- Literal << keys in YAML files are no longer emitted without quotes (docker/cli#7461), which fixes the confusing parse failures people hit when a key happened to look like a merge operator.
- The daemon no longer hangs on container, image, and system API requests under load (moby/moby#54041). If you have been restarting dockerd during CI bursts, this is your fix.
- BuildKit updated to v0.34.2 (moby/moby#54107).
Upgrade notes
Package upgrades are the usual path: apt or dnf on Linux, or the Docker Desktop point release if you drive Engine through Desktop. Restarting dockerd bounces containers that were not started with a restart policy, so schedule it like any other daemon restart. On Swarm managers, upgrade one node at a time and watch the raft quorum. The leader-change attack vector means the window right after a manager rotation is exactly when you want the patched SwarmKit in place, so rotate managers only after every node is on 29.9.3.
One contextual note worth filing: 29.9.2 from October 20 already replaced the Go runtime to reject certificate chains that include eight revoked eMudhra intermediates. If registry pulls or pushes started failing TLS verification in late October, that change, not this release, is the cause. Affected registries need a replacement chain that avoids those intermediates.
Worth it?
Yes, without much debate. Three of the six CVEs can take down or compromise a host rather than just a container, and two of them arrive through inputs that clients and registries control. This is a maintenance window I would book today rather than next sprint.