chore(deps): update module github.com/docker/docker to v28 [security]#381
Closed
renovate[bot] wants to merge 1 commit intomasterfrom
Closed
chore(deps): update module github.com/docker/docker to v28 [security]#381renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: renovate[bot] <bot@renovateapp.com>
HadrienPatte
added a commit
that referenced
this pull request
Aug 22, 2025
Both dependabot (#380) and renovate (#381) tried to update this dep, but it looks like they both missed the `go mod tidy` step, leading to broken PRs with failing CI. I ran: ``` go get github.com/docker/docker@v28.3.3 go mod tidy ``` Note: since we're bumping this dep anyway I bumped it all the way to its latest version (`v28.3.3`) instead of just the minimum version required for the security fix (`v28.0.0`). Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte
added a commit
that referenced
this pull request
Aug 22, 2025
Both dependabot (#380) and renovate (#381) tried to update `docker/docker` to v28 but there's some incompatibility between that module and the version of `google/go-containerregistry` currently used here so they both need to be updated. I ran: ``` go get github.com/docker/docker@v28.3.3 go get github.com/google/go-containerregistry@v0.20.6 go mod tidy ``` Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Member
|
383 |
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
tklauser
pushed a commit
that referenced
this pull request
Sep 16, 2025
Both dependabot (#380) and renovate (#381) tried to update `docker/docker` to v28 but there's some incompatibility between that module and the version of `google/go-containerregistry` currently used here so they both need to be updated. I ran: ``` go get github.com/docker/docker@v28.3.3 go get github.com/google/go-containerregistry@v0.20.6 go mod tidy ``` Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v27.1.1+incompatible->v28.0.0+incompatibleGitHub 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
--internalor 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:
References
https://firewalld.org/
https://firewalld.org/documentation/howto/reload-firewalld.html
Release Notes
docker/docker (github.com/docker/docker)
v28.0.0+incompatibleCompare Source
v27.5.1+incompatibleCompare Source
v27.5.0+incompatibleCompare Source
v27.4.1+incompatibleCompare Source
v27.4.0+incompatibleCompare Source
v27.3.1+incompatibleCompare Source
v27.3.0+incompatibleCompare Source
v27.2.1+incompatibleCompare Source
v27.2.0+incompatibleCompare Source
v27.1.2+incompatibleCompare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.