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

Moby's Firewalld reload removes bridge network isolation

moby · moby

Official source article: GitHub GHSA-4VQ8-7JFC-9CVP ↗. Check the applicable product and release in the original source.

3.3LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% 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: No default targetRemediation target: Normal maintenance

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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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
Debian trixietrixie · sourcedocker.ioAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcedocker.ioAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcedocker.ioAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcedocker.ioAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 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 6 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 6 Oct 2026
Open-source package ranges4 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 0; fixed 25.0.1325.0.13OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/docker/dockerSEMVER: introduced 26.0.0-rc1; fixed 28.0.028.0.0OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/docker/docker<= 25.0.1225.0.13GitHub advisory ↗upstream repository advisory · 27 Mar 2026
gogithub.com/docker/docker>= 26.0.0-rc1, < 28.0.028.0.0GitHub advisory ↗upstream repository advisory · 27 Mar 2026
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-54410 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/moby/moby: Moby's Firewalld reload removes bridge network isolation
15 known affected

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

  • multicluster-engine/agent-service-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-service-8-rhel8 as a component of Multicluster Engine for Kubernetes
  • multicluster-engine/assisted-service-9-rhel9 as a component of Multicluster Engine for Kubernetes
  • multicluster-globalhub/multicluster-globalhub-grafana-rhel9 as a component of Multicluster Global Hub
  • rhacm2/acm-grafana-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
  • rhceph/grafana-rhel9 as a component of Red Hat Ceph Storage 5
  • rhel9/grafana as a component of Red Hat Ceph Storage 5
  • rhceph/grafana-rhel9 as a component of Red Hat Ceph Storage 6
  • rhel9/grafana as a component of Red Hat Ceph Storage 6
  • rhceph/grafana-rhel9 as a component of Red Hat Ceph Storage 8
  • rhel9/grafana as a component of Red Hat Ceph Storage 8
  • openshift4/ose-agent-installer-api-server-rhel8 as a component of Red Hat OpenShift Container Platform 4
Summary
A firewall state management issue was found in the Moby project. When firewalld reloads, Docker fails to recreate iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This issue breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.22/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
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-23166

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 actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
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. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.

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. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.

Why

The product does not initialize a critical resource.

How

An attacker operating through local access may attempt exploitation with low privileges. 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. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.

Why

The product does not initialize a critical resource.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Missing Initialization of Resource → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
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:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-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-1094Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-14505 Référence CVE CVE-2025-14914 https://www.cve.org/CVERecord?id=CVE-2025-14914 Référence CVE CVE-2025-14920 https://www.cve.org/CVERecord?id=CVE-2025-14920 Référence CVE CVE-2025-15599 https://www.cve.org/CVERecord?id=CVE-2025-15599 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=CVE-2025-40026 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47279 https://www.cve.org/CVERecord?id=CVE-2025-47279 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48913 https://www.cve.org/CVERecord?id=CVE-2025-48913 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-6170 https://www.cve.org/CVERecord?id=CVE-2025-6170 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-66168 https://www.cve.org/CVERecord?id=CVE-2025-66168 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2025-36442 Référence CVE CVE-2025-38351 https://www.cve.org/CVERecord?id=CVE-2025-38351 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-47911 https://www.cve.org/CVERecord?id=CVE-2025-47911 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-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-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 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-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58190 https://www.cve.org/CVERecord?id=CVE-2025-58190 Référence CVE CVE-2025-58767 https://www.cve.org/CVERecord?id=CVE-2025-58767 Référence CVE CVE-2025-59059 https://www.cve.org/CVERecord?id=CVE-2025-59059 Référence CVE CVE-2025-5914 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2025-47909 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-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 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-53859 https://www.cve.org/CVERecord?id=CVE-2025-53859 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55130 https://www.cve.org/CVERecord?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 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=

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

ecord?id=CVE-2025-50106 Référence CVE CVE-2025-50537 https://www.cve.org/CVERecord?id=CVE-2025-50537 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 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-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-55183 https://www.cve.org/CVERecord?id=CVE-2025-55183 Référence CVE CVE-2025-55184 https://www.cve.org/CVERecord?id=CVE-2025-55184 Référence CVE CVE-2025-57752 https://www.cve.org/CVERecord?id=CVE-2025-57752 Référence CVE CVE-2025-57822 https://www.cve.org/CVERecord?id=CVE-2025-57822 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=

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

cord?id=CVE-2025-4947 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-5025 https://www.cve.org/CVERecord?id=CVE-2025-5025 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-52999 https://www.cve.org/CVERecord?id=CVE-2025-52999 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-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55753 https://www.cve.org/CVERecord?id=CVE-2025-55753 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-58058 https://www.cve.org/CVERecord?id=CVE-2025-58058 Référence CVE CVE-2025-58098 https://www.cve.org/CVERecord?id=CVE-2025-58098 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=

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

d?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=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=

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

cord?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=CVE-2025-55160 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-50104 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-52434 https://www.cve.org/CVERecord?id=CVE-2025-52434 Référence CVE CVE-2025-53023 https://www.cve.org/CVERecord?id=CVE-2025-53023 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-53506 https://www.cve.org/CVERecord?id=CVE-2025-53506 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-54798 https://www.cve.org/CVERecord?id=CVE-2025-54798 Référence CVE CVE-2025-55193 https://www.cve.org/CVERecord?id=CVE-2025-55193 Référence CVE CVE-2025-55248 https://www.cve.org/CVERecord?id=CVE-2025-55248 Référence CVE CVE-2025-55315 https://www.cve.org/CVERecord?id=CVE-2025-55315 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-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-48988 https://www.cve.org/CVERecord?id=CVE-2025-48988 Référence CVE CVE-2025-48989 https://www.cve.org/CVERecord?id=CVE-2025-48989 Référence CVE CVE-2025-49125 https://www.cve.org/CVERecord?id=CVE-2025-49125 Référence CVE CVE-2025-52434 https://www.cve.org/CVERecord?id=CVE-2025-52434 Référence CVE CVE-2025-52999 https://www.cve.org/CVERecord?id=CVE-2025-52999 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-6020 https://www.cve.org/CVERecord?id=CVE-2025-6020 Référence CVE CVE-2025-6965 https://www.cve.org/CVERecord?id=CVE-2025-6965 Référence CVE CVE-2025-7425 https://www.cve.org/CVERecord?id=CVE-2025-7425 Référence CVE CVE-2025-8941 https://www.cve.org/CVERecord?id=CVE-2025-8941 Référence CVE CVE-2025-9288 https://www.cve.org/CVERecord?id=CVE-2025-9288 Gestion détaillée du document le 04 septembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propo

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-012222Moby 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.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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-23166
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    <= 25.0.12 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    <= 25.0.12 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.22/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-23166↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-4VQ8-7JFC-9CVP↗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-54410 · cve.blacktree.nl