BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-54388High confidence

Moby's Firewalld reload makes published container ports accessible from remote hosts

moby · moby

Official source article: GitHub GHSA-X4RX-4GW3-53P4 ↗. Check the applicable product and release in the original source.

5.1MediumCVSS 4.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs moby moby and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitydockerVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.28.3.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitydockerVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.28.3.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Debian trixietrixie · sourcedocker.ioNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcedocker.ioNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcedocker.ioNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcedocker.ioNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsdocker.ioUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsdocker.io-appUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/docker/dockerSEMVER: introduced 28.2.0; fixed 28.3.328.3.3OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/docker/docker>= 28.2.0, < 28.3.328.3.3GitHub advisory ↗upstream repository advisory · 10 Sep 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-54388 · CSAF 2.0 · revision 32 · interimSUSE Product Security TeamCVE-2025-54388
43 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • docker as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • docker-bash-completion as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • docker as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • docker-bash-completion as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • docker-buildx as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • docker as component of SUSE Linux Enterprise High Performance Computing 15
  • docker-bash-completion as component of SUSE Linux Enterprise High Performance Computing 15
  • docker as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • docker-bash-completion as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • docker as component of SUSE Linux Enterprise Server 15 SP1
  • docker-bash-completion as component of SUSE Linux Enterprise Server 15 SP1
  • docker as component of SUSE Linux Enterprise Server 15 SP2-LTSS
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-23167

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not initialize a critical resource.

How

An attacker operating through an adjacent network may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not initialize a critical resource.

How

An attacker operating through an adjacent network may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → Missing Initialization of Resource → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-909 ↗

CWE-909: Missing Initialization of Resource. The product does not initialize a critical resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VILowVulnerable-system integrity: A successful attack can cause a limited loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCLowSubsequent-system confidentiality: A successful attack can cause a limited loss.SILowSubsequent-system integrity: A successful attack can cause a limited loss.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-909
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20250806Security Bulletin 06 Aug 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 Aug 2025, published on 6 August 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-47912 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48060 https://www.cve.org/CVERecord?id=CVE-2025-48060 Référence CVE CVE-2025-48989 https://www.cve.org/CVERecord?id=CVE-2025-48989 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=CVE-2025-55199 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55754 https://www.cve.org/CVERecord?id=CVE-2025-55754 Référence CVE CVE-2025-58058 https://www.cve.org/CVERecord?id=CVE-2025-58058 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1129Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-47907 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-2025-47910 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-57352 https://www.cve.org/CVERecord?id=CVE-2025-57352 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2025-53506 Référence CVE CVE-2025-5351 https://www.cve.org/CVERecord?id=CVE-2025-5351 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-53643 https://www.cve.org/CVERecord?id=CVE-2025-53643 Référence CVE CVE-2025-5372 https://www.cve.org/CVERecord?id=CVE-2025-5372 Référence CVE CVE-2025-53859 https://www.cve.org/CVERecord?id=CVE-2025-53859 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-53905 https://www.cve.org/CVERecord?id=CVE-2025-53905 Référence CVE CVE-2025-53906 https://www.cve.org/CVERecord?id=CVE-2025-53906 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-54801 https://www.cve.org/CVERecord?id=CVE-2025-54801 Référence CVE CVE-2025-54874 https://www.cve.org/CVERecord?id=CVE-2025-54874 Référence CVE CVE-2025-54988 https://www.cve.org/CVERecord?id=CVE-2025-54988 Référence CVE CVE-2025-55004 https://www.cve.org/CVERecord?id=CVE-2025-55004 Référence CVE CVE-2025-55005 https://www.cve.org/CVERecord?id=CVE-2025-55005 Référence CVE CVE-2025-55154 https://www.cve.org/CVERecord?id=CVE-2025-55154 Référence CVE CVE-2025-55160 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0935Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2025-46818 Référence CVE CVE-2025-46819 https://www.cve.org/CVERecord?id=CVE-2025-46819 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-49844 https://www.cve.org/CVERecord?id=CVE-2025-49844 Référence CVE CVE-2025-5115 https://www.cve.org/CVERecord?id=CVE-2025-5115 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-5914 https://www.cve.org/CVERecord?id=CVE-2025-5914 Référence CVE CVE-2025-7425 https://www.cve.org/CVERecord?id=CVE-2025-7425 Référence CVE CVE-2025-8058 https://www.cve.org/CVERecord?id=CVE-2025-8058 Référence CVE CVE-2025-8869 https://www.cve.org/CVERecord?id=CVE-2025-8869 Gestion détaillée du document le 29 octobre 2025 Version initiale Aler

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-013425Moby Project の Moby におけるリソースの初期化の不備に関する脆弱性

Moby Project の Moby には、リソースの初期化の不備に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
28.3.3.
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 Jul 2025 · Last source change 30 Jul 2025, 13:38 UTC · CWE-909 · Missing Initialization of Resource

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-23167
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-23167↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference · GitHub GHSA-X4RX-4GW3-53P4↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-54388 · cve.blacktree.nl