<?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>Tue, 06 Oct 2026 16:52:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-278266</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-278266</link>
      <description>EUVD-2026-278266</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-278266</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31946</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31946</link>
      <description>&lt;p&gt;OpenOlat is an open source web-based e-learning platform for teaching, learning, assessment and communication. From version 10.5.4 to before version 20.2.5, OpenOLAT&amp;#39;s OpenID Connect implicit flow implementation does not verify JWT signatures. The JSONWebToken.parse() method silently discards the signature segment of the compact JWT (header.payload.signature), and the getAccessToken() methods in both OpenIdConnectApi and OpenIdConnectFullConfigurableApi only validate claim-level fields (issuer, audience, state, nonce) without any cryptographic signature verification against the Identity Provider&amp;#39;s JWKS endpoint. This issue has been patched in version 20.2.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenOlat is an open source web-based e-learning platform for teaching, learning, assessment and communication. From version 10.5.4 to before version 20.2.5, OpenOLAT&amp;#39;s OpenID Connect implicit flow implementation does not verify JWT signatures. The JSONWebToken.parse() method silently discards the signature segment of the compact JWT (header.payload.signature), and the getAccessToken() methods in both OpenIdConnectApi and OpenIdConnectFullConfigurableApi only validate claim-level fields (issuer, audience, state, nonce) without any cryptographic signature verification against the Identity Provider&amp;#39;s JWKS endpoint. This issue has been patched in version 20.2.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31946</guid>
    </item>
  </channel>
</rss>
