Read the docs

Docker Engine overlay encryption rules not restored after firewalld reload

Priority LOW 31CWE-693Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
None · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-693.

Summary

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 let outgoing VXLAN datagrams bypass IPsec encryption and remove protection against incoming cleartext VXLAN traffic. dockerd does not log the condition, which persists until the encrypted network's last local endpoint is removed and another is added, or dockerd is restarted, and each further firewalld event repeats it.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00307 23rd percentileScored 2026-11-16
Fix Fixed Docker Engine (Docker): 29.9.3Moby (Moby): v2.0.0-beta.29

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
DockerDocker Enginebefore 29.9.329.9.3Patch availableCNA
mobyMobybefore v2.0.0-beta.29v2.0.0-beta.29Patch availableCNA
  • Docker Engine VendorDocker Affected before 29.9.3 Fixed in 29.9.3 Patch available CNA
  • Moby Vendormoby Affected before v2.0.0-beta.29 Fixed in v2.0.0-beta.29 Patch available CNA

Remediation

Upgrade Docker Engine to 29.9.3 or Moby to v2.0.0-beta.29, which fix the flaw. Versions before these are affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA Docker Engine (Docker) Fixed in 29.9.3
  • Fix · CNA Moby (Moby) Fixed in v2.0.0-beta.29

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-115538
  2. 2026-11-12 Priority changed: MEDIUM → LOW
  3. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2019-11833 Docker Desktop flaw lets local users gain privileges KEVCVSS 3.1HIGH 7.8
  • TI-2019-04061 runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows… CVSS 3.1HIGH 8.6
  • TI-2025-08316 Docker Desktop allows unauthenticated access to Docker Engine API from containers CVSS 4.0CRITICAL 9.3
  • TI-2025-02823 Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion CVSS 4.0HIGH 7.3
  • TI-2026-14229 Tar extraction in moby/go-archive can write outside the destination directory via link following CVSS 4.0HIGH 7.1
  • TI-2023-21271 Docker Machine through 0.16.2 allows an attacker, who has control of a worker node, to… CVSS 3.1MEDIUM 6.5
See all 137 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences