Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 14, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/docker/docker v27.5.1+incompatible -> v28.0.0+incompatible age confidence

GitHub Vulnerability Alerts

CVE-2025-54410

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


Release Notes

docker/docker (github.com/docker/docker)

v28.0.0+incompatible

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch 2 times, most recently from 290e71f to af66915 Compare August 25, 2025 01:05
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch from af66915 to 90f7565 Compare August 27, 2025 19:57
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch 4 times, most recently from fb592af to 0181b45 Compare September 7, 2025 09:39
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch 4 times, most recently from 42e4093 to 73491ce Compare October 14, 2025 10:54
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch from 73491ce to 93f6583 Compare October 22, 2025 05:03
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch 3 times, most recently from 57ac182 to fd6aa77 Compare November 9, 2025 17:34
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch from fd6aa77 to 9c108a0 Compare November 17, 2025 01:41
@renovate renovate bot force-pushed the renovate/go-github.com-docker-docker-vulnerability branch from 9c108a0 to e2e17a5 Compare November 20, 2025 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant