CVE-2025-54388: Moby's Firewalld reload makes published container ports accessible from remote hosts
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: moby moby 28.3.3.
Low priority for now. Upgrade to moby moby 28.3.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-909
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.1
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mobyproject | moby | cpe:2.3:a:mobyproject:moby |
Using moby? Add it to your stack and be the first to know about CVEs like this one. (Docker)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mobyproject moby28.2.0 and later · before 28.3.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
moby moby
- >= 28.2.0, < 28.3.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.22 | docker | before 28.3.3-r0 | 28.3.3-r0 |
| Go | github.com/docker/docker | from 28.2.0 · before 28.3.3 | 28.3.3 |
| Go | github.com/docker/docker | from 28.2.0+incompatible · before 28.3.3+incompatible | 28.3.3+incompatible |
| openSUSE:Leap 15.6 | docker | before 28.3.3_ce-150000.230.1 | 28.3.3_ce-150000.230.1 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
| openSUSE:Leap 16.0 | docker | before 28.5.1_ce-160000.4.1 | 28.5.1_ce-160000.4.1 |
| openSUSE:Tumbleweed | docker | before 28.3.3_ce-26.1 | 28.3.3_ce-26.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250811T192933-1.1 | 0.0.20250811T192933-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | docker | before 28.3.3_ce-150000.230.1 | 28.3.3_ce-150000.230.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250814T182633-150000.1.98.1 | 0.0.20250814T182633-150000.1.98.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | docker | before 28.3.3_ce-98.137.1 | 28.3.3_ce-98.137.1 |
| SUSE:Linux Enterprise Server 16.0 | docker | before 28.5.1_ce-160000.4.1 | 28.5.1_ce-160000.4.1 |
| SUSE:Linux Micro 6.0 | docker | before 28.3.3_ce-6.1 | 28.3.3_ce-6.1 |
| SUSE:Linux Micro 6.1 | docker | before 28.4.0_ce-slfo.1.1_6.1 | 28.4.0_ce-slfo.1.1_6.1 |
Same product
mobyproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-28840moby/moby's dockerd daemon encrypted overlay network may be unauthenticated35Monitor
- CVE-2024-36623moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent writ32Monitor
- CVE-2024-24557Moby classic builder cache poisoning31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-36620Nov 29, 2024 · moby v25.0.0 - v26.0.2 is vulnerable to NULL Pointer Dereference via daemon/images/image_history.go.26Monitor
- ← EarlierCVE-2024-36621Nov 29, 2024 · moby v25.0.5 is affected by a Race Condition in builder/builder-next/adapters/snapshot/layer.go.26Monitor
- Later →CVE-2025-54410Jul 30, 2025 · Moby's Firewalld reload removes bridge network isolation20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| moby moby | 28.3.3 · description | Vendor (CNA) |
| alpine:docker | 28.3.3-r0 · Alpine:v3.22 | Package registry (OSV) |
| Go:github.com/docker/docker | 28.3.3 | Package registry (OSV) |
| Go:github.com/docker/docker | 28.3.3+incompatible | Package registry (OSV) |
| opensuse:docker | 28.3.3_ce-150000.230.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:docker | 28.3.3_ce-150000.230.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:docker | 28.3.3_ce-98.137.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20250814T182633-150000.1.98.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-544100 days apartMoby's Firewalld reload removes bridge network isolation20Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-909 · Missing Initialization of ResourceCVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.