Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Configure firewalld to preserve other applications' iptables rules: use FirewallBackend=nftables with a build that includes commit b7faa74db15e2d1ebd9fdfcdc7579874d3a2fa87 (firewalld 2.0.0 or later, or the RHEL backports listed in configurations), and remove all firewalld direct configuration. Alternatively, restart dockerd after every firewalld reload, stop, or start to restore the encryption rules; this also restarts the node's Swarm tasks. As defense in depth, block incoming traffic to the VXLAN port (by default, UDP port 4789) at the Internet boundary. This prevents injection from outside the boundary but does not protect the confidentiality of traffic between nodes.
Tue, 10 Nov 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Docker Engine overlay-network encryption rules are not restored after a firewalld reload | |
| Weaknesses | CWE-693 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Docker
Published:
Updated: 2026-11-10T19:58:45.360Z
Reserved: 2026-10-22T19:45:01.367Z
Link: CVE-2026-115538
No data.
Status : Received
Published: 2026-11-10T20:18:03.747
Modified: 2026-11-10T20:18:03.747
Link: CVE-2026-115538
No data.
OpenCVE Enrichment
No data.