<?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>Thu, 15 Oct 2026 15:02:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-188099</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-188099</link>
      <description>EUVD-2026-188099</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-188099</guid>
    </item>
    <item>
      <title>fkie_cve-2023-32186</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-32186</link>
      <description>&lt;p&gt;A Allocation of Resources Without Limits or Throttling vulnerability in SUSE RKE2  allows attackers with access to K3s servers apiserver/supervisor port (TCP 6443) cause denial of service.
This issue affects RKE2: from 1.24.0 before 1.24.17+rke2r1, from v1.25.0 before v1.25.13+rke2r1, from v1.26.0 before v1.26.8+rke2r1, from v1.27.0 before v1.27.5+rke2r1, from v1.28.0 before v1.28.1+rke2r1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Allocation of Resources Without Limits or Throttling vulnerability in SUSE RKE2  allows attackers with access to K3s servers apiserver/supervisor port (TCP 6443) cause denial of service.
This issue affects RKE2: from 1.24.0 before 1.24.17+rke2r1, from v1.25.0 before v1.25.13+rke2r1, from v1.26.0 before v1.26.8+rke2r1, from v1.27.0 before v1.27.5+rke2r1, from v1.28.0 before v1.28.1+rke2r1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-32186</guid>
    </item>
    <item>
      <title>GHSA-p45j-vfv5-wprq — RKE2 supervisor port is vulnerable to unauthenticated remote denial-of-service (DoS) attack via TLS SAN stuffing attack</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p45j-vfv5-wprq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/rke2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An issue was found in RKE2 where an attacker with network access to RKE2 servers&amp;#39; supervisor port (TCP 9345) can force the TLS server to add entries to the certificate&amp;#39;s Subject Alternative Name (SAN) list, through a stuffing attack, until the certificate grows so large that it exceeds the maximum size allowed by TLS client implementations. OpenSSL for example will raise an `excessive message size` error when this occurs. No authentication is necessary to perform this attack, only the ability to perform a TLS handshake against the supervisor port (TCP 9345).&lt;/p&gt;
&lt;p&gt;Affected servers will continue to operate, but clients (server or agent nodes) will fail to establish new connections when joining or rejoining the cluster, thus leading to a denial of service (DoS) attack.&lt;/p&gt;
&lt;p&gt;### Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to a fixed release:
- v1.28.1+rke2r1
- v1.27.5+rke2r1
- v1.26.8+rke2r1
- v1.25.13+rke2r1
- 1.24.17+rke2r1&lt;/p&gt;
&lt;p&gt;If you are using RKE2 1.27 or earlier, you must also add the parameter `tls-san-security: true` to the RKE2 configuration to enable enhanced security for the supervisor&amp;#39;s TLS SAN list. This option defaults to `true` starting with RKE2 1.28.&lt;/p&gt;
&lt;p&gt;Note that this flag changes the behavior of RKE2&amp;#39;s supervisor listener. You should ensure that you configure `node-external-ip` on servers that will be connected to via an external IP, and add `tls-san` entries for any load-balancers or VIP addresses that will be associated with the supervisor port. External IPs and load-balancer/VIP add…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/rke2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An issue was found in RKE2 where an attacker with network access to RKE2 servers&amp;#39; supervisor port (TCP 9345) can force the TLS server to add entries to the certificate&amp;#39;s Subject Alternative Name (SAN) list, through a stuffing attack, until the certificate grows so large that it exceeds the maximum size allowed by TLS client implementations. OpenSSL for example will raise an `excessive message size` error when this occurs. No authentication is necessary to perform this attack, only the ability to perform a TLS handshake against the supervisor port (TCP 9345).&lt;/p&gt;
&lt;p&gt;Affected servers will continue to operate, but clients (server or agent nodes) will fail to establish new connections when joining or rejoining the cluster, thus leading to a denial of service (DoS) attack.&lt;/p&gt;
&lt;p&gt;### Remediation&lt;/p&gt;
&lt;p&gt;Upgrade to a fixed release:
- v1.28.1+rke2r1
- v1.27.5+rke2r1
- v1.26.8+rke2r1
- v1.25.13+rke2r1
- 1.24.17+rke2r1&lt;/p&gt;
&lt;p&gt;If you are using RKE2 1.27 or earlier, you must also add the parameter `tls-san-security: true` to the RKE2 configuration to enable enhanced security for the supervisor&amp;#39;s TLS SAN list. This option defaults to `true` starting with RKE2 1.28.&lt;/p&gt;
&lt;p&gt;Note that this flag changes the behavior of RKE2&amp;#39;s supervisor listener. You should ensure that you configure `node-external-ip` on servers that will be connected to via an external IP, and add `tls-san` entries for any load-balancers or VIP addresses that will be associated with the supervisor port. External IPs and load-balancer/VIP add…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p45j-vfv5-wprq</guid>
    </item>
    <item>
      <title>gsd-2023-32186</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-32186</link>
      <description>gsd-2023-32186</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-32186</guid>
    </item>
  </channel>
</rss>
