LowGHSA-4vq8-7jfc-9cvpCVE-2025-54410GO-2025-3829

Moby firewalld reload removes bridge network isolation

Published 29 Jul 2025 · Updated 10 Sept 2026

Is your project on an affected github.com/docker/docker?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<25.0.13
Fixed in
25.0.13
Update to the fixed version for your release line, for example:go get github.com/docker/docker@v25.0.13
Affected
>=26.0.0-rc1 <28.0.0
Fixed in
28.0.0
Update to the fixed version for your release line, for example:go get github.com/docker/docker@v28.0.0

Details

Moby 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 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

Is GHSA-4vq8-7jfc-9cvp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/docker/docker, and gives you the command that fixes it.

More advisories for github.com/docker/docker

  • LowCVE-2026-41568Race condition in 'docker cp' in github.com/docker/docker allows creation of arbitrary files · 25 Jun 2026
  • LowCVE-2026-41567Docker: 'PUT /containers/{id}/archive' executes container binary on the host in github.com/docker/docker · 25 Jun 2026
  • LowCVE-2026-42306Race condition in 'docker cp' in github.com/docker/docker allows bind mount redirection · 25 Jun 2026
  • HighCVE-2026-42306Docker: Race condition in docker cp allows bind mount redirection to host path · 18 May 2026
  • MediumCVE-2026-41568Docker: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap · 18 May 2026
  • HighCVE-2026-41567Docker: `PUT /containers/{id}/archive` executes container binary on the host · 18 May 2026
All 66 advisories for github.com/docker/docker

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.