DOCKER ENGINE · CVE-2026-115538 · Runtime
FIX → 29.9.3 · v2.0.0-beta.29 ✓ verified
Moby's overlay network driver does not restore iptables rules for encrypted overlay networks after firewalld deletes them. As a result, VXLAN traffic can bypass IPsec encryption and incoming cleartext VXLAN traffic is no longer blocked.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Swarm nodes running Docker Engine before 29.9.3 with at least one container or task on an encrypted overlay network (off by default) and firewalld running in a setup where it deletes other apps' iptables rules (iptables backend, older nftables-backend builds, or any direct rules). A firewalld reload, restart or start then leaves VXLAN traffic in cleartext and lets someone who can send UDP to port 4789 inject frames. Skip it if you do not use encrypted overlay networks, do not run Swarm, or have no firewalld.
Not affected if nftables-with-firewalld-2.0, no-encrypted-overlay, no-firewalld, no-swarm, single-host-bridge-networks
Who cares docker, firewalld, linux, moby, overlay-network, swarm
Moby's overlay network driver does not restore the iptables rules for encrypted overlay networks after firewalld deletes them. Unlike other Docker Engine networking components, the overlay driver does not handle firewalld reload or start signals over D-Bus. The missing rules cause outgoing VXLAN datagrams to bypass IPsec encryption and remove the protection against incoming cleartext VXLAN traffic. The condition is not logged by dockerd and persists until the encrypted network's last local endpoint is removed and another is added, or dockerd is restarted. Each further firewalld event repeats the condition.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 29.9.3 · v2.0.0-beta.29
29.9.3 (moby v2.0.0-beta.29)2.0.0 (or RHEL backports 1.2.5-1.el9 / 0.9.11-9.el8) and no direct rules, or restart dockerd after every firewalld reload/stop/start (this restarts the node's Swarm tasks)