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. In versions 28.2.0 through 28.3.2, when the firewalld service is reloaded it removes all iptables rules including those created by Docker. While Docker should automatically recreate these rules, versions before 28.3.3 fail to recreate the specific rules that block external access to containers. This means that after a firewalld reload, containers with ports published to localhost (like 127.0.0.1:8080) become accessible from remote machines that have network routing to the Docker bridge, even though they should only be accessible from the host itself. The vulnerability only affects explicitly published ports - unpublished ports remain protected. This issue is fixed in version 28.3.3.
History

Thu, 31 Jul 2025 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Docker
Docker engine
Docker moby
Mirantis
Mirantis mirantis Container Runtime
Mobyproject
Mobyproject moby
Vendors & Products Docker
Docker engine
Docker moby
Mirantis
Mirantis mirantis Container Runtime
Mobyproject
Mobyproject moby

Thu, 31 Jul 2025 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.2, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}

threat_severity

Moderate


Wed, 30 Jul 2025 14:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 30 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Description 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. In versions 28.2.0 through 28.3.2, when the firewalld service is reloaded it removes all iptables rules including those created by Docker. While Docker should automatically recreate these rules, versions before 28.3.3 fail to recreate the specific rules that block external access to containers. This means that after a firewalld reload, containers with ports published to localhost (like 127.0.0.1:8080) become accessible from remote machines that have network routing to the Docker bridge, even though they should only be accessible from the host itself. The vulnerability only affects explicitly published ports - unpublished ports remain protected. This issue is fixed in version 28.3.3.
Title Moby's Firewalld reload makes published container ports accessible from remote hosts
Weaknesses CWE-909
References
Metrics cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published: 2025-07-30T13:24:06.849Z

Updated: 2025-07-30T13:38:07.559Z

Reserved: 2025-07-21T16:12:20.734Z

Link: CVE-2025-54388

cve-icon Vulnrichment

Updated: 2025-07-30T13:38:00.757Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-07-30T14:15:28.693

Modified: 2025-07-31T18:42:37.870

Link: CVE-2025-54388

cve-icon Redhat

Severity : Moderate

Publid Date: 2025-07-30T13:24:06Z

Links: CVE-2025-54388 - Bugzilla