Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-54410: Moby's Firewalld reload removes bridge network isolation

MediumCVSS 5.2 · v3.1—No exploit Fix available

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.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: github.com/docker/docker (Go) 28.0.0, 25.0.13+incompatible, 25.0.13; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1.

Low priority for now. Upgrade to github.com/docker/docker (Go) 28.0.0, 25.0.13+incompatible, 25.0.13; govulncheck-vulndb (openSUSE:Leap 15.6) 0.0.20250814T182633-150000.1.98.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250811T192933-1.1 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. 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.

Published
Jul 30, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.2
CNA · GitHub_M
3.3
1.9 point gap

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A: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.

Follow CVE-2025-54410

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
mobyprojectmoby

Using moby? Add it to your stack and be the first to know about CVEs like this one. (Docker)

Watch new CVEs for moby

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or is weaponized

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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

    • <= 25.0.12affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mobyproject mobybefore 25.0.13

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12docker.iofrom 0—
Gogithub.com/docker/dockerfrom 26.0.0-rc1 · before 28.0.028.0.0
Gogithub.com/docker/dockerbefore 25.0.13+incompatible25.0.13+incompatible
Gogithub.com/docker/dockerbefore 25.0.1325.0.13
openSUSE:Leap 15.6govulncheck-vulndbbefore 0.0.20250814T182633-150000.1.98.10.0.20250814T182633-150000.1.98.1
openSUSE:Tumbleweedgovulncheck-vulndbbefore 0.0.20250811T192933-1.10.0.20250811T192933-1.1
openSUSE:Tumbleweedkubectl-retinabefore 1.3.1-1.11.3.1-1.1
SUSE:Linux Enterprise Module for Package Hub 15 SP6govulncheck-vulndbbefore 0.0.20250814T182633-150000.1.98.10.0.20250814T182633-150000.1.98.1

Other highest-scoring records for the same primary product.

  • CVE-2023-28840moby/moby's dockerd daemon encrypted overlay network may be unauthenticated
    35Monitor
  • CVE-2024-36623moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent…
    32Monitor
  • CVE-2024-24557Moby classic builder cache poisoning
    31Monitor

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
  • ← EarlierCVE-2025-54388Jul 30, 2025 · Moby's Firewalld reload makes published container ports accessible from remote hosts
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/docker/docker25.0.13Package registry (OSV)
Go:github.com/docker/docker25.0.13+incompatiblePackage registry (OSV)
Go:github.com/docker/docker28.0.0Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20250814T182633-150000.1.98.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kubectl-retina1.3.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:govulncheck-vulndb0.0.20250814T182633-150000.1.98.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-543880 days apartMoby's Firewalld reload makes published container ports accessible from remote hosts
    20Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

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

nvd-primary

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.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records