<?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, 03 Oct 2026 14:25:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-260396</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260396</link>
      <description>EUVD-2026-260396</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260396</guid>
    </item>
    <item>
      <title>fkie_cve-2025-64432</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-64432</link>
      <description>&lt;p&gt;KubeVirt is a virtual machine management add-on for Kubernetes. Versions 1.5.3 and below, and 1.6.0 contained a flawed implementation of the Kubernetes aggregation layer&amp;#39;s authentication flow which could enable bypass of RBAC controls. It was discovered that the virt-api component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the extension-apiserver-authentication configmap. Failre to validate certain fields in the client TLS certificate may allow an attacker to bypass existing RBAC controls by directly communicating with the aggregated API server, impersonating the Kubernetes API server and its aggregator component. This issue is fixed in versions 1.5.3 and 1.6.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;KubeVirt is a virtual machine management add-on for Kubernetes. Versions 1.5.3 and below, and 1.6.0 contained a flawed implementation of the Kubernetes aggregation layer&amp;#39;s authentication flow which could enable bypass of RBAC controls. It was discovered that the virt-api component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the extension-apiserver-authentication configmap. Failre to validate certain fields in the client TLS certificate may allow an attacker to bypass existing RBAC controls by directly communicating with the aggregated API server, impersonating the Kubernetes API server and its aggregator component. This issue is fixed in versions 1.5.3 and 1.6.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-64432</guid>
    </item>
    <item>
      <title>GHSA-38jw-g2qx-4286 — KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-38jw-g2qx-4286</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: kubevirt.io/kubevirt&lt;/p&gt;
&lt;p&gt;### Summary
_Short summary of the problem. Make the impact and severity as clear as possible.&lt;/p&gt;
&lt;p&gt;A flawed implementation of the Kubernetes aggregation layer&amp;#39;s authentication flow could enable bypassing RBAC controls.&lt;/p&gt;
&lt;p&gt;### Details
_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._&lt;/p&gt;
&lt;p&gt;It was discovered that the `virt-api` component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the `extension-apiserver-authentication` configmap.&lt;/p&gt;
&lt;p&gt;The Kubernetes API server proxies received client requests through a component called aggregator (part of K8S&amp;#39;s API server), and authenticates to the `virt-api` server using a certificate signed by the CA specified via the `--requestheader-client-ca-file` CLI flag. This CA bundle is primarily used in the context of aggregated API servers, where the Kubernetes API server acts as a trusted front-end proxy forwarding requests.&lt;/p&gt;
&lt;p&gt;While this is the most common use case, the same CA bundle can also support less common scenarios, such as issuing certificates to [authenticating](how-kubernetes-certificates-work) front-end [proxies](https://deepwiki.com/kubernetes/apiserver/7.1-authentication#request-header-authentication). These proxies can be deployed by organizations to extend Kubernetes&amp;#39; native authentication mecha…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: kubevirt.io/kubevirt&lt;/p&gt;
&lt;p&gt;### Summary
_Short summary of the problem. Make the impact and severity as clear as possible.&lt;/p&gt;
&lt;p&gt;A flawed implementation of the Kubernetes aggregation layer&amp;#39;s authentication flow could enable bypassing RBAC controls.&lt;/p&gt;
&lt;p&gt;### Details
_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._&lt;/p&gt;
&lt;p&gt;It was discovered that the `virt-api` component fails to correctly authenticate the client when receiving API requests over mTLS. In particular, it fails to validate the CN (Common Name) field in the received client TLS certificates against the set of allowed values defined in the `extension-apiserver-authentication` configmap.&lt;/p&gt;
&lt;p&gt;The Kubernetes API server proxies received client requests through a component called aggregator (part of K8S&amp;#39;s API server), and authenticates to the `virt-api` server using a certificate signed by the CA specified via the `--requestheader-client-ca-file` CLI flag. This CA bundle is primarily used in the context of aggregated API servers, where the Kubernetes API server acts as a trusted front-end proxy forwarding requests.&lt;/p&gt;
&lt;p&gt;While this is the most common use case, the same CA bundle can also support less common scenarios, such as issuing certificates to [authenticating](how-kubernetes-certificates-work) front-end [proxies](https://deepwiki.com/kubernetes/apiserver/7.1-authentication#request-header-authentication). These proxies can be deployed by organizations to extend Kubernetes&amp;#39; native authentication mecha…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-38jw-g2qx-4286</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-64432 — KubeVirt Affected by an Authentication Bypass in Kubernetes Aggregation Layer</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-64432</link>
      <description>msrc_CVE-2025-64432</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-64432</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20281-1 — Security update for kubevirt</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20281-1</link>
      <description>&lt;p&gt;Security update for kubevirt&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for kubevirt&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20281-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:20551-1 — Security update for kubevirt</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:20551-1</link>
      <description>&lt;p&gt;Security update for kubevirt&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for kubevirt&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:20551-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2563 — Microsoft Azure Linux: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2563</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Microsoft Azure Linux und Microsoft Windows ausnutzen um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, die Authentifizierung zu umgehen,  Spoofing-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Microsoft Azure Linux und Microsoft Windows ausnutzen um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, die Authentifizierung zu umgehen,  Spoofing-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2563</guid>
    </item>
  </channel>
</rss>
