Moby's Firewalld reload removes bridge network isolation
cve-program · CVE-2025-54410
PublishedMoby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.
Read the publisher's advisoryeuvd · EUVD-2025-23166
PublishedMoby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.
Read the publisher's advisorynvd · CVE-2025-54410
PublishedMoby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.
Read the publisher's advisoryosv · GHSA-4vq8-7jfc-9cvp
PublishedMoby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (dockerd), which is developed as [moby/moby](https://github.com/moby/moby) is commonly referred to as Docker, or Docker Engine. Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks. ### Impact The iptables rules created by Docker are removed when firewalld is reloaded using, for example "firewall-cmd --reload", "killall -HUP firewalld", or "systemctl reload firewalld". When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that isolate containers in different bridge networks from each other are not re-created. Once these rules have been removed, containers have access to any port, on any container, in any non-internal bridge network, running on the Docker host. Containers running in networks created with `--internal` or equivalent have no access to other networks. Containers that are only connected to these networks remain isolated after a firewalld reload. Where Docker Engine is not running in the host's network namespace, it is unaffected. Including, for example, Rootless Mode, and Docker Desktop. ### Patches Moby releases 28.0.0 and newer are not affected. A fix is available in moby release 25.0.13. ### Workarounds After reloading firewalld, either: - Restart the docker daemon, - Re-create bridge networks, or - Use rootless mode. ### References https://firewalld.org/ https://firewalld.org/documentation/howto/reload-firewalld.html
Read the publisher's advisoryosv · GO-2025-3829
PublishedMoby firewalld reload removes bridge network isolation in github.com/docker/docker
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2025-54410 · CVE overview and exploitation status
cve-program · CVE-2025-54410
- https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
- https://firewalld.org/documentation/howto/reload-firewalld.html
euvd · EUVD-2025-23166
- https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
- https://firewalld.org/documentation/howto/reload-firewalld.html
nvd · CVE-2025-54410
- https://firewalld.org/documentation/howto/reload-firewalld.html
- https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
osv · GHSA-4vq8-7jfc-9cvp
- https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
- https://nvd.nist.gov/vuln/detail/CVE-2025-54410
- https://github.com/moby/moby/pull/49443
- https://github.com/moby/moby/pull/49728
- https://firewalld.org/documentation/howto/reload-firewalld.html
- https://github.com/moby/moby