<?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>Fri, 16 Oct 2026 08:04:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276432</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276432</link>
      <description>EUVD-2026-276432</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276432</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32254</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32254</link>
      <description>&lt;p&gt;Kube-router is a turnkey solution for Kubernetes networking. Prior to version 2.8.0, Kube-router&amp;#39;s proxy module does not validate externalIPs or loadBalancer IPs before programming them into the node&amp;#39;s network configuration. Version 2.8.0 contains a patch for the issue. Available workarounds include enabling DenyServiceExternalIPs feature gate, deploying admission policy, restricting service creation RBAC, monitoring service changes, and applying BGP prefix filtering.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kube-router is a turnkey solution for Kubernetes networking. Prior to version 2.8.0, Kube-router&amp;#39;s proxy module does not validate externalIPs or loadBalancer IPs before programming them into the node&amp;#39;s network configuration. Version 2.8.0 contains a patch for the issue. Available workarounds include enabling DenyServiceExternalIPs feature gate, deploying admission policy, restricting service creation RBAC, monitoring service changes, and applying BGP prefix filtering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32254</guid>
    </item>
    <item>
      <title>GHSA-phqm-jgc3-qf8g — Kube-router Proxy Module Blindly Trusts ExternalIPs/LoadBalancer IPs Enabling Cluster-Wide Traffic Hijacking and DNS DoS</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-phqm-jgc3-qf8g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cloudnativelabs/kube-router/v2&lt;/p&gt;
&lt;p&gt;# kube-router Proxy Module Does Not Validate ExternalIPs or LoadBalancer IPs Against Configured Ranges&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;This issue primarily affects multi-tenant clusters where untrusted users are granted namespace-scoped permissions to create or modify Services. Single-tenant clusters or clusters where all Service creators are trusted are not meaningfully affected.&lt;/p&gt;
&lt;p&gt;The kube-router proxy module&amp;#39;s `buildServicesInfo()` function directly copies IPs from `Service.spec.externalIPs` and `status.loadBalancer.ingress` into node-level network configuration (kube-dummy-if interface, IPVS virtual services, LOCAL routing table) without validating them against the `--service-external-ip-range` parameter. A user with namespace-scoped Service CRUD permissions can bind arbitrary VIPs on all cluster nodes or cause denial of service to critical cluster services such as kube-dns.&lt;/p&gt;
&lt;p&gt;The `--service-external-ip-range` parameter is only consumed by the netpol (network policy) module for firewall RETURN rules. The proxy module never reads this configuration, creating a gap between administrator expectations and actual enforcement.&lt;/p&gt;
&lt;p&gt;Kubernetes&amp;#39; `DenyServiceExternalIPs` Feature Gate was introduced in v1.22 and remains disabled by default through v1.31, meaning most clusters allow Services to carry externalIPs without any admission control.&lt;/p&gt;
&lt;p&gt;**Note:** This vulnerability class is not unique to kube-router. The upstream Kubernetes project classified the equivalent issue as [CVE-2020-8554](https://github.co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/cloudnativelabs/kube-router/v2&lt;/p&gt;
&lt;p&gt;# kube-router Proxy Module Does Not Validate ExternalIPs or LoadBalancer IPs Against Configured Ranges&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;This issue primarily affects multi-tenant clusters where untrusted users are granted namespace-scoped permissions to create or modify Services. Single-tenant clusters or clusters where all Service creators are trusted are not meaningfully affected.&lt;/p&gt;
&lt;p&gt;The kube-router proxy module&amp;#39;s `buildServicesInfo()` function directly copies IPs from `Service.spec.externalIPs` and `status.loadBalancer.ingress` into node-level network configuration (kube-dummy-if interface, IPVS virtual services, LOCAL routing table) without validating them against the `--service-external-ip-range` parameter. A user with namespace-scoped Service CRUD permissions can bind arbitrary VIPs on all cluster nodes or cause denial of service to critical cluster services such as kube-dns.&lt;/p&gt;
&lt;p&gt;The `--service-external-ip-range` parameter is only consumed by the netpol (network policy) module for firewall RETURN rules. The proxy module never reads this configuration, creating a gap between administrator expectations and actual enforcement.&lt;/p&gt;
&lt;p&gt;Kubernetes&amp;#39; `DenyServiceExternalIPs` Feature Gate was introduced in v1.22 and remains disabled by default through v1.31, meaning most clusters allow Services to carry externalIPs without any admission control.&lt;/p&gt;
&lt;p&gt;**Note:** This vulnerability class is not unique to kube-router. The upstream Kubernetes project classified the equivalent issue as [CVE-2020-8554](https://github.co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-phqm-jgc3-qf8g</guid>
    </item>
  </channel>
</rss>
