<?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, 08 Oct 2026 19:33:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-248454</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-248454</link>
      <description>EUVD-2026-248454</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-248454</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53940</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53940</link>
      <description>&lt;p&gt;Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one&amp;#39;s own. In versions 6.1.0-alpha.4 and below, Quiet&amp;#39;s API for backend/frontend communication was using an insecure, not constant-time comparison function for token verification. This allowed for a potential timing attack where an attacker would try different token values and observe tiny differences in the response time (wrong characters fail faster) to guess the whole token one character at a time. This is fixed in version 6.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Quiet is an alternative to team chat apps like Slack, Discord, and Element that does not require trusting a central server or running one&amp;#39;s own. In versions 6.1.0-alpha.4 and below, Quiet&amp;#39;s API for backend/frontend communication was using an insecure, not constant-time comparison function for token verification. This allowed for a potential timing attack where an attacker would try different token values and observe tiny differences in the response time (wrong characters fail faster) to guess the whole token one character at a time. This is fixed in version 6.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53940</guid>
    </item>
  </channel>
</rss>
