CVE-2025-54388: moby — Fix

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.

Is your site exposed to CVE-2025-54388?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

4.6

MEDIUM

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Weakness Type (CWE)

CWE-909 CWE-909

Affected Products

Vendor	Product	Versions
mobyproject	moby	28.2.0 — 28.3.3

References

Advisories & Patches

https://github.com/moby/moby/commit/bea959c7b793b32a893820b97c4eadc7c87fabb0 https://github.com/moby/moby/pull/50506 https://github.com/moby/moby/security/advisories/GHSA-x4rx-4gw3-53p4

Frequently Asked Questions

What is CVE-2025-54388? +

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. It has a CVSS v3.1 base score of 4.6 (MEDIUM).

How severe is CVE-2025-54388? +

CVE-2025-54388 has a CVSS v3.1 score of 4.6 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance.

What products are affected by CVE-2025-54388? +

CVE-2025-54388 affects products from mobyproject, specifically: moby. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2025-54388? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2024-53845

ESPTouch is a connection protocol for internet of things devices. In the ESPTouchV2 protocol, while there is an option to …

CVE-2024-8178 8.8

The ctl_write_buffer and ctl_read_buffer functions allocated memory to be returned to userspace, without initializing it. Malicious software running in a …

CVE-2024-43873 7.8

In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: always initialize seqpacket_allow There are two issues around seqpacket_allow: …

CVE-2024-9780 7.8

ITS dissector crash in Wireshark 4.4.0 allows denial of service via packet injection or crafted capture file

CVE-2025-8117 7.5

PAD CMS improperly initializes parameter used for password recovery, which allows to change password for any user that did not …

CVE-2022-49865 7.1

In the Linux kernel, the following vulnerability has been resolved: ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network …

CVE-2025-54388