CVE-2025-54410
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMoby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWhen firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks from each other, allowing any container on one bridge network to access all ports on any container on a different bridge network on the same host. This breaks network segmentation that should exist between isolated container workloads.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 25.0.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker/Moby versionRun `docker version` or `dockerd --version` to determine the installed Moby versionAffected if The version is below 25.0.13 (e.g., 25.0.12, 25.0.x, or earlier)
-
Verify firewalld is activeRun `systemctl is-active firewalld` or `firewall-cmd --state`Affected if firewalld is running on the host system
-
List Docker bridge networksRun `docker network ls` and filter for bridge type networksAffected if Multiple bridge networks exist on the host
-
Inspect iptables isolation rulesRun `iptables -L DOCKER-ISOLATION -v -n` or `iptables -S DOCKER-ISOLATION` to check if inter-bridge isolation rules are presentAffected if After a firewalld reload, the DOCKER-ISOLATION chain is missing or does not contain rules preventing cross-bridge traffic
You are affected if running Moby < 25.0.13 with firewalld active and multiple bridge networks, and the DOCKER-ISOLATION iptables rules are missing after a firewalld reload.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped25.0.13
Implement the documented workaround (restart docker daemon after firewalld reloads, recreate bridge networks, or use rootless mode), and plan for version upgrade to 25.0.13 or later when available.
Moby 25.0.13 or later
- Back up all containers, images, volumes, and Docker configuration files
- Stop the Docker daemon: sudo systemctl stop docker
- Upgrade Moby/Docker Engine to version 25.0.13 or later using your package manager (e.g., apt-get update && apt-get install moby, or yum install moby)
- Start the Docker daemon: sudo systemctl start docker
- Verify the upgrade: docker version
- Test network isolation by creating two bridge networks and confirming containers cannot reach each other across different bridge networks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data