<?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>Sat, 17 Oct 2026 07:53:11 +0000</lastBuildDate>
    <item>
      <title>BIT-cilium-2023-27594 — Cilium vulnerable to potential network policy bypass when routing IPv6 traffic</title>
      <link>https://cve.radiocsirt.org/vuln/bit-cilium-2023-27594</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: cilium&lt;/p&gt;
&lt;p&gt;Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.&lt;/p&gt;
&lt;p&gt;This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: cilium&lt;/p&gt;
&lt;p&gt;Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.&lt;/p&gt;
&lt;p&gt;This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-cilium-2023-27594</guid>
    </item>
    <item>
      <title>EUVD-2026-218845</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218845</link>
      <description>EUVD-2026-218845</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218845</guid>
    </item>
    <item>
      <title>fkie_cve-2023-27594</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-27594</link>
      <description>&lt;p&gt;Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.&lt;/p&gt;
&lt;p&gt;This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Cilium is a networking, observability, and security solution with an eBPF-based dataplane. Prior to versions 1.11.15, 1.12.8, and 1.13.1, under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled.&lt;/p&gt;
&lt;p&gt;This issue only manifests when Cilium is routing IPv6 traffic and NodePorts are used to route traffic to pods. IPv6 and endpoint routes are both disabled by default.&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions 1.11.15, 1.12.8, and 1.13.1. As a workaround, disable IPv6 routing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-27594</guid>
    </item>
    <item>
      <title>GHSA-8fg8-jh2h-f2hc — Potential network policy bypass when routing IPv6 traffic</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8fg8-jh2h-f2hc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cilium/cilium&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. Only IPv6 traffic is impacted by this vulnerability.&lt;/p&gt;
&lt;p&gt;This issue only manifests when:
* Cilium is routing IPv6 traffic, and
* Kube-proxy is used for service handling, and
* NodePorts are used to route traffic to pods.&lt;/p&gt;
&lt;p&gt;IPv6 is disabled by default. Cilium&amp;#39;s kube-proxy replacement feature is not affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions &amp;gt;=1.11.15, &amp;gt;=1.12.8, &amp;gt;=1.13.1&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Disable IPv6 routing (IPv6 is disabled by default).&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Yusuke Suzuki for both highlighting and fixing the issue.&lt;/p&gt;
&lt;p&gt;## For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).&lt;/p&gt;
&lt;p&gt;As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cilium/cilium&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Under specific conditions, Cilium may misattribute the source IP address of traffic to a cluster, identifying external traffic as coming from the host on which Cilium is running. As a consequence, network policies for that cluster might be bypassed, depending on the specific network policies enabled. Only IPv6 traffic is impacted by this vulnerability.&lt;/p&gt;
&lt;p&gt;This issue only manifests when:
* Cilium is routing IPv6 traffic, and
* Kube-proxy is used for service handling, and
* NodePorts are used to route traffic to pods.&lt;/p&gt;
&lt;p&gt;IPv6 is disabled by default. Cilium&amp;#39;s kube-proxy replacement feature is not affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The problem has been fixed and is available on versions &amp;gt;=1.11.15, &amp;gt;=1.12.8, &amp;gt;=1.13.1&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Disable IPv6 routing (IPv6 is disabled by default).&lt;/p&gt;
&lt;p&gt;## Acknowledgements&lt;/p&gt;
&lt;p&gt;The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to Yusuke Suzuki for both highlighting and fixing the issue.&lt;/p&gt;
&lt;p&gt;## For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).&lt;/p&gt;
&lt;p&gt;As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: security@cilium.io - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8fg8-jh2h-f2hc</guid>
    </item>
    <item>
      <title>gsd-2023-27594</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-27594</link>
      <description>gsd-2023-27594</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-27594</guid>
    </item>
  </channel>
</rss>
