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.

The remote openSUSE 16 host has packages installed that are affected by a vulnerability as referenced in the openSUSE- SU-2026:20057-1 advisory.

    Changes in docker:

    - Update to Docker 28.5.1-ce. See upstream changelog online at       <https://docs.docker.com/engine/release-notes/28/#2851>

    - Update to Docker 28.5.0-ce. See upstream changelog online at       <https://docs.docker.com/engine/release-notes/28/#2850>

    - Update to docker-buildx v0.29.0. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.29.0>

    - Remove git-core recommends on SLE. Most SLE systems have       installRecommends=yes by default and thus end up installing git with Docker.
      bsc#1250508

      This feature is mostly intended for developers (docker build git://) so       most users already have the dependency installed, and the error when git is       missing is fairly straightforward (so they can easily figure out what they       need to install).

    - Update to docker-buildx v0.28.0. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.28.0>

    - Update to Docker 28.4.0-ce. See upstream changelog online at       <https://docs.docker.com/engine/release-notes/28/#2840>
      * Fixes a nil pointer panic in docker push. bsc#1248373

    - Update warnings and errors related to docker buildx ... so that they       reference our openSUSE docker-buildx packages.

    - Enable building docker-buildx for SLE15 systems with SUSEConnect secret       injection enabled. PED-12534 PED-8905 bsc#1247594

      As docker-buildx does not support our SUSEConnect secret injection (and some       users depend docker build working transparently), patch the docker CLI so       that docker build will no longer automatically call docker buildx build,       effectively making DOCKER_BUILDKIT=0 the default configuration. Users can       manually use docker buildx ... commands or set DOCKER_BUILDKIT=1 in order       to opt-in to using docker-buildx.

      Users can silence the docker build warning by setting DOCKER_BUILDKIT=0       explicitly.

      In order to inject SCC credentials with docker-buildx, users should use

        RUN --mount=type=secret,id=SCCcredentials zypper -n ...

      in their Dockerfiles, and

        docker buildx build --secret id=SCCcredentials,src=/etc/zypp/credentials.d/SCCcredentials,type=file .

      when doing their builds.

    - Update to Docker 28.3.3-ce. See upstream changelog online at       <https://docs.docker.com/engine/release-notes/28/#2833>       CVE-2025-54388 bsc#1247367

    - Update to docker-buildx v0.26.1. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.26.1>

    - Update to docker-buildx v0.26.0. Upstream changelog:
      <https://github.com/docker/buildx/releases/tag/v0.26.0>

Tenable has extracted the preceding description block directly from the SUSE 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 Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2025:0667 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-54388:
    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.

Tenable has extracted the preceding description block directly from the Tencent Linux 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 remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:02914-1 advisory.

    - Update to Docker 28.3.3-ce.
    - CVE-2025-54388: Fixed a bug where firewalld when reloaded can make published container ports accessible     from remote hosts. (bsc#1247367)

Tenable has extracted the preceding description block directly from the SUSE 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 remote SUSE Linux SLES12 host has packages installed that are affected by a vulnerability as referenced in the SUSE- SU-2025:02913-1 advisory.

    - Update to Docker 28.3.3-ce.
    - CVE-2025-54388: Fixed a bug where firewalld when reloaded can make published container ports accessible     from remote hosts. (bsc#1247367)

Tenable has extracted the preceding description block directly from the SUSE 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. 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. (CVE-2025-54388)

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

The version of the Docker Engine (Moby) installed on the remote host is between 28.2.0 to 28.3.2 It is therefore affected by an vulnerability that exposes local ports to the network. 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.

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	Severity
291339	openSUSE 16 Security Update : docker (openSUSE-SU-2026:20057-1)	Nessus	SuSE Local Security Checks	medium
253473	TencentOS Server 4: moby (TSSA-2025:0667)	Nessus	Tencent Local Security Checks	medium
252932	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : docker (SUSE-SU-2025:02914-1)	Nessus	SuSE Local Security Checks	medium
252920	SUSE SLES12 Security Update : docker (SUSE-SU-2025:02913-1)	Nessus	SuSE Local Security Checks	medium
251987	Linux Distros Unpatched Vulnerability : CVE-2025-54388	Nessus	Misc.	medium
243284	Docker Engine 28.2 < 28.3.3 Local Docker Ports Exposed to Network	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-54388

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium