<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 17:57:50 +0000</lastBuildDate>
    <item>
      <title>GHSA-x4rx-4gw3-53p4 — Moby firewalld reload makes published container ports accessible from remote hosts</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-x4rx-4gw3-53p4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/docker/docker&lt;/p&gt;
&lt;p&gt;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. The Moby daemon component (dockerd), which is developed as [moby/moby](https://github.com/moby/moby) is commonly referred to as Docker, or Docker Engine.&lt;/p&gt;
&lt;p&gt;Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The iptables rules created by Docker are removed when firewalld is reloaded using, for example &amp;#34;firewall-cmd --reload&amp;#34;, &amp;#34;killall -HUP firewalld&amp;#34;, or &amp;#34;systemctl reload firewalld&amp;#34;.&lt;/p&gt;
&lt;p&gt;When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that prevent packets arriving on a host interface from reaching container addresses are not re-created.&lt;/p&gt;
&lt;p&gt;Once these rules have been removed, a remote host configured with a route to a Docker bridge network can access published ports, even when those ports were only published to a loopback address. Unpublished ports remain inaccessible.&lt;/p&gt;
&lt;p&gt;For example, following a firewalld reload on a Docker host with address `192.168.0.10` and a bridge network with subnet `172.17.0.0/16`, running the following command on another host in the local network will give it access to published port…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/docker/docker&lt;/p&gt;
&lt;p&gt;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. The Moby daemon component (dockerd), which is developed as [moby/moby](https://github.com/moby/moby) is commonly referred to as Docker, or Docker Engine.&lt;/p&gt;
&lt;p&gt;Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The iptables rules created by Docker are removed when firewalld is reloaded using, for example &amp;#34;firewall-cmd --reload&amp;#34;, &amp;#34;killall -HUP firewalld&amp;#34;, or &amp;#34;systemctl reload firewalld&amp;#34;.&lt;/p&gt;
&lt;p&gt;When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that prevent packets arriving on a host interface from reaching container addresses are not re-created.&lt;/p&gt;
&lt;p&gt;Once these rules have been removed, a remote host configured with a route to a Docker bridge network can access published ports, even when those ports were only published to a loopback address. Unpublished ports remain inaccessible.&lt;/p&gt;
&lt;p&gt;For example, following a firewalld reload on a Docker host with address `192.168.0.10` and a bridge network with subnet `172.17.0.0/16`, running the following command on another host in the local network will give it access to published port…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-x4rx-4gw3-53p4</guid>
    </item>
  </channel>
</rss>
