<?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:06:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07969</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07969</link>
      <description>bdu:2026-07969</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07969</guid>
    </item>
    <item>
      <title>EUVD-2026-325179</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-325179</link>
      <description>EUVD-2026-325179</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-325179</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46389</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46389</link>
      <description>&lt;p&gt;UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS Core&amp;#39;s Identity deployment. In versions 0.11.0 through 0.26.0, a logic error in the `client-kubernetes-secret` Keycloak client authenticator (shipped by `uds-identity-config` and consumed by UDS Core) causes the submitted `client_secret` to be overwritten with the mounted Kubernetes secret before comparison. An attacker who can reach the Keycloak token endpoint and knows a `client_id` using this authenticator can authenticate as that client with any `client_secret` value and obtain OAuth2 tokens scoped to the client&amp;#39;s service account. In the case of the `uds-operator` client this token can be used to registry/modify other clients. Version 0.26.1 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;UDS Identity Config builds the Keycloak configuration image (realm, plugins, theme, truststore, JARs) consumed by UDS Core&amp;#39;s Identity deployment. In versions 0.11.0 through 0.26.0, a logic error in the `client-kubernetes-secret` Keycloak client authenticator (shipped by `uds-identity-config` and consumed by UDS Core) causes the submitted `client_secret` to be overwritten with the mounted Kubernetes secret before comparison. An attacker who can reach the Keycloak token endpoint and knows a `client_id` using this authenticator can authenticate as that client with any `client_secret` value and obtain OAuth2 tokens scoped to the client&amp;#39;s service account. In the case of the `uds-operator` client this token can be used to registry/modify other clients. Version 0.26.1 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46389</guid>
    </item>
  </channel>
</rss>
