Vulnerability DatabaseCVE-2026-115538

CVE-2026-115538: 
Docker vulnerability analysis and mitigation

Overview

CVE-2026-115538 is a protection mechanism failure in Moby's overlay network driver that causes iptables rules for encrypted overlay networks to not be reinstalled after firewalld deletes them. Affecting Docker Engine versions before 29.9.3 and Moby (github.com/moby/moby/v2) before v2.0.0-beta.29, the flaw results in VXLAN traffic bypassing IPsec encryption and losing spoofing protections. It was published on November 10, 2026, and carries a CVSS v4.0 base score of 7.0 (High) (GitHub Advisory).

Technical details

The root cause is classified as CWE-693 (Protection Mechanism Failure): unlike other Docker Engine networking components, the overlay network driver does not subscribe to firewalld reload or start signals over D-Bus, so it never reinstates its iptables rules after firewalld flushes them. The overlay driver relies on two critical iptables rules: one in the mangle table's OUTPUT chain that marks outgoing VXLAN datagrams for IPsec policy enforcement, and one in the filter table's INPUT chain that discards incoming cleartext VXLAN datagrams tagged with the encrypted network's VNI. When firewalld reloads (e.g., via firewall-cmd --reload, package upgrades, or service restarts), these rules are deleted and not restored, causing outgoing traffic to be sent in cleartext and removing injection protections. The condition is silent — dockerd does not log the loss of rules — and persists until the encrypted network's last local endpoint is cycled or dockerd is restarted (GitHub Advisory).

Impact

After a triggering firewalld event, affected nodes transmit VXLAN datagrams of encrypted overlay networks in cleartext, exposing container-to-container traffic to any observer on the network path between Swarm nodes. Additionally, the loss of INPUT chain rules allows an attacker who can send UDP datagrams to the node's VXLAN port (default UDP 4789) to inject arbitrary Ethernet frames into the overlay network, enabling traffic manipulation and potential lateral movement within the Swarm cluster. The subsequent system confidentiality and integrity impacts are rated High, as sensitive inter-container communications and network integrity are both compromised (GitHub Advisory).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the publication date. The EPSS score is 0.0, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires specific preconditions: the target node must be part of a Docker Swarm with at least one task on an encrypted overlay network, and firewalld must be running in a configuration that flushes other applications' iptables rules (e.g., FirewallBackend=iptables, or nftables without upstream commit b7faa74, or with direct firewalld rules configured) (GitHub Advisory).

Exploitation steps

  1. Reconnaissance: Identify Docker Swarm nodes running encrypted overlay networks and confirm that firewalld is active on the target host using tools like Shodan or network scanning.
  2. Trigger firewalld reload: Wait for or induce a firewalld reload event — this can occur naturally during package upgrades, configuration management runs (firewall-cmd --reload), or firewalld service restarts — which flushes the overlay driver's iptables rules without them being restored.
  3. Confirm rule absence: Verify that the iptables mangle OUTPUT and filter INPUT rules for the encrypted overlay network's VNI are missing (e.g., iptables -t mangle -L OUTPUT and iptables -L INPUT show no VXLAN/VNI-specific rules).
  4. Intercept cleartext traffic: Position a network observer (e.g., tcpdump -i <interface> udp port 4789) on the network path between Swarm nodes to capture VXLAN datagrams now transmitted in cleartext, exposing container traffic.
  5. Inject Ethernet frames: Send crafted UDP datagrams to the target node's VXLAN port (UDP 4789) tagged with the target overlay network's VNI to inject arbitrary Ethernet frames into the encrypted overlay network, as described in CVE-2023-28840 (GitHub Advisory).

Indicators of compromise

  • Network: Unencrypted VXLAN UDP traffic (port 4789) observed between Swarm nodes that should be using IPsec-encrypted overlay networks; unexpected cleartext Ethernet frames tagged with known overlay VNIs captured via packet inspection.
  • Logs: Absence of expected iptables rules in iptables -t mangle -L OUTPUT and iptables -L INPUT for overlay network VNIs following a firewalld reload event; no corresponding dockerd log entries warning of rule loss (the condition is silent by design).
  • System State: Running iptables-save | grep VXLAN or checking for VNI-specific mangle/filter rules returns empty results on a node with active encrypted overlay network endpoints; firewall-cmd --reload events in system journal (journalctl -u firewalld) correlating with traffic anomalies (GitHub Advisory).

Mitigation and workarounds

Upgrade to Docker Engine 29.9.3 or Moby v2.0.0-beta.29, which include the fix for this vulnerability (GitHub Advisory). If immediate upgrade is not possible, the following workarounds can mitigate the risk:

  • Configure firewalld with FirewallBackend=nftables using a build that includes upstream commit b7faa74 (firewalld 2.0.0+, or RHEL backports firewalld-1.2.5-1.el9 / firewalld-0.9.11-9.el8), and remove any direct firewalld rules or chains.
  • Restart dockerd after every firewalld reload, stop, or start event (note: this also restarts Swarm tasks).
  • Block incoming traffic on UDP port 4789 at the network boundary to prevent external frame injection (does not protect traffic confidentiality between nodes).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

bionic (esm-apps)

docker.io

Unknown

devel

docker.io

Unknown

focal (esm-apps)

docker.io

Unknown

jammy

docker.io

Unknown

jammy (esm-apps)

docker.io

Unknown

noble

docker.io

Unknown

noble (esm-apps)

docker.io

Unknown

resolute

docker.io

Unknown

RHEL / CentOS

Affected

OpenShift

openshift4/ose-agent-installer-api-server-rhel8

Affected

RHEL 9

Not Affected

RHEL 10

Not Affected

Alpine

Fixed

edge

docker: 29.9.3-r0

Fixed

Source: This report was generated using AI

Related Docker vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-115539HIGH7.7
  • Docker logoDocker
  • docker.io
NoYesNov 10, 2026
CVE-2026-115538HIGH7
  • Docker logoDocker
  • github.com/moby/moby/v2
NoYesNov 10, 2026
CVE-2026-97054MEDIUM5.9
  • Go logoGo
  • rhc-worker-playbook
NoYesNov 11, 2026
CVE-2026-121520MEDIUM4.5
  • Docker logoDocker
  • podmansh
NoNoNov 03, 2026
CVE-2026-121542LOW1.8
  • Docker logoDocker
  • docker-buildx
NoNoNov 03, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management