CVE-2025-54388
ADVISORY - githubSummary
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 prevent packets arriving on a host interface from reaching container addresses are not re-created.
Once these rules have been removed, a remote host configured with a route to a Docker bridge network can access published ports, even when those ports were only published to a loopback address. Unpublished ports remain inaccessible.
For example, following a firewalld reload on a Docker host with address 192.168.0.10 and a bridge network with subnet 172.17.0.0/16, running the following command on another host in the local network will give it access to published ports on container addresses in that network: ip route add 172.17.0.0/16 via 192.168.0.10.
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 older than 28.2.0 are not affected. A fix is available in moby release 28.3.3.
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
Common Weakness Enumeration (CWE)
Missing Initialization of Resource
Missing Initialization of Resource
GitHub
2.1
CVSS SCORE
5.1medium| Package | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
|---|---|---|---|---|---|
| github.com/docker/docker | golang | - | - | >=28.2.0,<28.3.3 | 28.3.3 |
| github.com/docker/docker | golang | - | - | >=0.0.0-20250528125821-0e2cc22d36ae,<0.0.0-20250725081316-bea959c7b793 | 0.0.0-20250725081316-bea959c7b793 |
CVSS:4 Severity and metrics
The CVSS metrics represent different qualitative aspects of a vulnerability that impact the overall score, as defined by the CVSS Specification.
The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service (DoS) by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.
The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker's payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system. Examples include: utilizing a website that has been modified to display malicious content when the page is rendered (most stored XSS or CSRF) running an application that calls a malicious binary that has been planted on the system using an application which generates traffic over an untrusted or compromised network (vulnerabilities requiring an on-path attacker).
There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
There is no impact to availability within the Vulnerable System.
There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
NIST
2.1
CVSS SCORE
5.1mediumAlpine
-
Debian
-
CVSS SCORE
N/AlowUbuntu
2.1
CVSS SCORE
4.6mediumGoLang
-
Chainguard
CGA-2wpp-7h77-hhwh
-
Chainguard
CGA-35hr-hhj2-vg7j
-
Chainguard
CGA-44pm-gg7c-86qh
-
Chainguard
CGA-648j-rm9v-9w37
-
Chainguard
CGA-6gf6-vg3p-j4rq
-
Chainguard
CGA-6q8v-9rgr-53r5
-
Chainguard
CGA-6v9j-7gjm-j39c
-
Chainguard
CGA-7345-2xg7-c3g2
-
Chainguard
CGA-78w4-4g4p-2qxp
-
Chainguard
CGA-7f4q-7gwf-75fm
-
Chainguard
CGA-7h53-78f9-pqf2
-
Chainguard
CGA-7qvg-m75m-wg6m
-
Chainguard
CGA-87jq-3xq3-88mr
-
Chainguard
CGA-995x-24xg-4g7w
-
Chainguard
CGA-cwcm-w9hq-7fm3
-
Chainguard
CGA-f336-9595-xhhh
-
Chainguard
CGA-f8qx-36h3-xhcp
-
Chainguard
CGA-ff8p-7jj4-8pp9
-
Chainguard
CGA-g4h8-8hhq-53qf
-
Chainguard
CGA-g8vq-4557-86gq
-
Chainguard
CGA-gfp9-vp8m-pq3x
-
Chainguard
CGA-h2cv-x6x5-frxh
-
Chainguard
CGA-hpqp-hv27-5w45
-
Chainguard
CGA-hvr8-95gx-r234
-
Chainguard
CGA-j5qg-pxmc-xf7p
-
Chainguard
CGA-jc6p-7cch-gq9h
-
Chainguard
CGA-jr8j-x3qr-2m8j
-
Chainguard
CGA-m3rw-447f-74hv
-
Chainguard
CGA-m43w-332q-6hx9
-
Chainguard
CGA-mcpf-9464-w9v7
-
Chainguard
CGA-mfx4-4243-8pcm
-
Chainguard
CGA-mhg2-w774-xpvw
-
Chainguard
CGA-p6f3-hjcr-55xq
-
Chainguard
CGA-p769-wcv6-r8pm
-
Chainguard
CGA-p96c-fhx6-wrfh
-
Chainguard
CGA-p9xj-r442-p45w
-
Chainguard
CGA-q44c-gjh9-4xw3
-
Chainguard
CGA-qq94-p29r-5xvc
-
Chainguard
CGA-r438-2hxc-qgqv
-
Chainguard
CGA-r4xv-7cw4-44hp
-
Chainguard
CGA-rf23-879g-gwp3
-
Chainguard
CGA-rh8h-j6r2-9g9j
-
Chainguard
CGA-rjj2-vcrv-2569
-
Chainguard
CGA-rqf7-wvx7-qf66
-
Chainguard
CGA-v47c-gvmr-9f8w
-
Chainguard
CGA-v9vq-9g9h-fqhx
-
Chainguard
CGA-vj5x-g835-345q
-
Chainguard
CGA-vpfq-2425-rvr3
-
Chainguard
CGA-vpgx-x5f3-7xqv
-
Chainguard
CGA-vr6r-qw7m-qgp4
-
Chainguard
CGA-vx37-rwm7-fpf2
-
Chainguard
CGA-wq2c-2jjx-8gp5
-
Chainguard
CGA-wrjq-vqjq-vvvx
-
Chainguard
CGA-wwgv-fvj8-v49x
-
Chainguard
CGA-wxj3-v34f-grrw
-
Chainguard
CGA-xm39-rjmw-8h5x
-
minimos
MINI-4cwj-66jg-mg79
-
minimos
MINI-8qm3-2cx8-fg69
-
minimos
MINI-h2rg-f4fw-h3gg
-
minimos
MINI-hmv2-mqvf-5h4v
-
minimos
MINI-qgrm-p58p-grwg
-
minimos
MINI-wwq2-cph2-34rc
-