<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 22:29:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-03462</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-03462</link>
      <description>bdu:2026-03462</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-03462</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0112 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0112</link>
      <description>certfr-2026-avi-0112</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0112</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-GU03381 — CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-gu03381</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: containerd&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the containerd package. The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: containerd&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the containerd package. The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-gu03381</guid>
    </item>
    <item>
      <title>EUVD-2026-263082</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-263082</link>
      <description>EUVD-2026-263082</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-263082</guid>
    </item>
    <item>
      <title>fkie_cve-2025-67499</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-67499</link>
      <description>&lt;p&gt;The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0  inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0  inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-67499</guid>
    </item>
    <item>
      <title>GHSA-jv3w-x3r3-g6rm — CNA Plugins Portmap nftables backend can intercept non-local traffic</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jv3w-x3r3-g6rm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containernetworking/plugins&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;The CNI `portmap` plugin allows containers to emulate opening a host port, forwarding that traffic to the container. For example, if a host has the IP 198.51.100.42, a container may request that all packets to `198.51.100.42:53` be forwarded to the container&amp;#39;s network.&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;When the `portmap` plugin is configured with the `nftables` backend, it inadvertently forwards all traffic with the same destination port as the host port, **ignoring the destination IP**. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node.&lt;/p&gt;
&lt;p&gt;In the given example above, traffic destined to port 53 but for a _separate container_ would still be captured and forwarded, even though it was not destined for the host.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Containers (i.e. kubernetes pods) that request HostPort forwarding can intercept all traffic destined for that port. This requires that the `portmap` plugin be explicitly configured to use the `nftables` backend. (The `iptables` backend is the default.)&lt;/p&gt;
&lt;p&gt;### Patches
This is fixed as of CNI plugins v1.9.0&lt;/p&gt;
&lt;p&gt;### Workarounds
Configure the `portmap` plugin to use the `iptables` backend. It does not have this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/containernetworking/plugins&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;The CNI `portmap` plugin allows containers to emulate opening a host port, forwarding that traffic to the container. For example, if a host has the IP 198.51.100.42, a container may request that all packets to `198.51.100.42:53` be forwarded to the container&amp;#39;s network.&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;When the `portmap` plugin is configured with the `nftables` backend, it inadvertently forwards all traffic with the same destination port as the host port, **ignoring the destination IP**. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node.&lt;/p&gt;
&lt;p&gt;In the given example above, traffic destined to port 53 but for a _separate container_ would still be captured and forwarded, even though it was not destined for the host.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Containers (i.e. kubernetes pods) that request HostPort forwarding can intercept all traffic destined for that port. This requires that the `portmap` plugin be explicitly configured to use the `nftables` backend. (The `iptables` backend is the default.)&lt;/p&gt;
&lt;p&gt;### Patches
This is fixed as of CNI plugins v1.9.0&lt;/p&gt;
&lt;p&gt;### Workarounds
Configure the `portmap` plugin to use the `iptables` backend. It does not have this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jv3w-x3r3-g6rm</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10261-1 — docker-29.2.1_ce-37.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10261-1</link>
      <description>&lt;p&gt;docker-29.2.1_ce-37.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;docker-29.2.1_ce-37.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10261-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-67499</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-67499</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-github-containernetworking-plugins, Ubuntu:22.04:LTS: golang-github-containernetworking-plugins, Ubuntu:24.04:LTS: golang-github-containernetworking-plugins, Ubuntu:25.10: golang-github-containernetworking-plugins, Ubuntu:26.04:LTS: golang-github-containernetworking-plugins&lt;/p&gt;
&lt;p&gt;The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: golang-github-containernetworking-plugins, Ubuntu:22.04:LTS: golang-github-containernetworking-plugins, Ubuntu:24.04:LTS: golang-github-containernetworking-plugins, Ubuntu:25.10: golang-github-containernetworking-plugins, Ubuntu:26.04:LTS: golang-github-containernetworking-plugins&lt;/p&gt;
&lt;p&gt;The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-67499</guid>
    </item>
  </channel>
</rss>
