Docker Engine 29.9.3 closes the regression that silently disabled Swarm overlay encryption
On November 3, 2026, Docker shipped patch 29.9.3: five CVEs, including a loss of encryption and anti-spoofing on Swarm overlay networks after firewalld flushes Docker’s iptables rules. Any Swarm fleet or firewalld host should move to 29.9.3 now.
November 3, 2026. Docker ships Engine 29.9.3, a security patch that closes five CVEs across Docker Engine, SwarmKit and BuildKit. November 3, 2026. The most dangerous, CVE-2026-115538, describes a regression where Swarm overlay networks lose their encryption and anti-spoofing protection after firewalld flushes Docker’s iptables rules. November 3, 2026. A second flaw, CVE-2026-115539, lets a worker node’s TLS certificate become a manager node certificate after a leader change. Why it matters: the encryption you believed was active may have fallen away without anything signalling it.
For a team running a Swarm in production, this is not a routine patch. It is dated, referenced proof that a network-security layer can degrade silently, at the whim of a firewall reload.
Five flaws, but only one that really matters for Swarm
Patch 29.9.3 breaks into three blocks. Docker Engine fixes two denial-of-service flaws: CVE-2026-116587, excessive CPU use when parsing crafted RSA keys (the go-jose library), and CVE-2026-116591, a panic when decompressing zstd data (the klauspost/compress library). BuildKit moves to v0.34.2 to close two further advisories — including one that let a malicious client set extended attributes outside the state directory, opening a privilege escalation on the host.
But the two flaws worth full attention are the Swarm ones. They strike at the core network promise of a cluster: that overlay traffic between nodes stays encrypted and that nobody can impersonate a legitimate node.
CVE-2026-115538: encryption that vanishes on a firewall reload
CVE-2026-115538 is the most insidious, because it is not an active exploit — it is state degradation. Swarm overlay networks can be created with IPsec encryption enabled (--opt encrypted). That option guarantees that traffic between nodes is encrypted and that packets cannot be spoofed.
The problem appears when firewalld — the dynamic firewall of RHEL, Fedora and derivatives — flushes Docker’s iptables rules during its own reload or when applying rules. After that flush, the protections Docker had laid down for the overlay data plane are not restored. The result: the overlay network keeps moving traffic, but without encryption or anti-spoofing, while the operator believes the opposite.
This is the worst kind of vulnerability for an SRE: no alarm fires, no log screams. The cluster runs, containers talk, and only a very careful audit of the iptables rules would reveal that the protection dropped. 29.9.3 fixes the regression by correctly restoring the rules after a firewalld flush.
CVE-2026-115539: the worker certificate that becomes a manager
The second, CVE-2026-115539, lives in SwarmKit, the orchestration component. It describes a flaw in certificate rotation: an attacker already holding a valid worker-node TLS certificate, with its private key, could obtain a manager-node certificate shortly after a leader change.
The context matters. In a Swarm, manager nodes hold the Raft log and the cluster’s secrets; worker nodes only execute tasks. Turning a worker certificate into a manager certificate means crossing the boundary between “execute” and “control”. The flaw requires a worker to be compromised already — it is not an entry point — but it converts a limited compromise into a compromise of the control plane. 29.9.3 ships a fixed SwarmKit.
What to do, and in what order
Remediation is a version bump, but the order matters for a Swarm. The standard rule applies: managers first, then workers, because the cluster can only drive an update while its control plane stays healthy.
# Check the deployed engine version (patch must be >= 29.9.3)
docker version --format '{{.Server.Version}}'
# On each node: managers first, then workers
sudo apt-get update && sudo apt-get install -y docker-ce docker-ce-cli containerd.io Two cases deserve extra attention. If you run a Swarm with overlay encryption enabled, treat 29.9.3 as critical — your protection may have dropped without a trace, and you need both to patch and to confirm the iptables rules are back in place. If you use firewalld on your hosts, the rule flush described by CVE-2026-115538 concerns you directly, even outside Swarm, whenever you have overlay networks or sensitive Docker rules.
Verdict
Docker Engine 29.9.3 is modest in volume, but it closes a regression that silently undermines a cluster’s network security.
If you run a Swarm, move to 29.9.3 now, managers first: the two Swarm flaws have no workaround, and one of them may already have disabled your overlay encryption without anything flagging it. If your hosts run firewalld, use the window to audit your iptables rules after patching — the update restores the protection, but a check costs one command. The trap is not the severity of the scores: it is that an encryption regression is invisible, and it can run for weeks before anyone notices.