The version of docker installed on the remote host is prior to 25.0.13-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2ECS-2025-076 advisory.

    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. (CVE-2025-54410)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2025-54410)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of docker installed on the remote host is prior to 25.0.13-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2DOCKER-2025-076 advisory.

    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. (CVE-2025-54410)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2025-1213 advisory.

    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. (CVE-2025-54410)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.13-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2NITRO-ENCLAVES-2025-070 advisory.

    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. (CVE-2025-54410)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of the Docker Engine (Moby) installed on the remote host is prior to 23.0.15 or 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 created with --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.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
271757	Amazon Linux 2 : docker, --advisory ALAS2ECS-2025-076 (ALASECS-2025-076)	Nessus	Amazon Linux Local Security Checks	10/28/2025	4/30/2026	medium
251986	Linux Distros Unpatched Vulnerability : CVE-2025-54410	Nessus	Misc.	8/19/2025	4/29/2026	medium
270535	Amazon Linux 2 : docker, --advisory ALAS2DOCKER-2025-076 (ALASDOCKER-2025-076)	Nessus	Amazon Linux Local Security Checks	10/15/2025	4/30/2026	medium
270553	Amazon Linux 2023 : docker (ALAS2023-2025-1213)	Nessus	Amazon Linux Local Security Checks	10/15/2025	4/30/2026	medium
270540	Amazon Linux 2 : docker, --advisory ALAS2NITRO-ENCLAVES-2025-070 (ALASNITRO-ENCLAVES-2025-070)	Nessus	Amazon Linux Local Security Checks	10/15/2025	4/30/2026	medium
243283	Docker Engine < 25.0.13 / 26.0 < 28.0.0 Network Isolation Failure	Nessus	Misc.	8/1/2025	5/1/2026	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium