<?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, 21 Nov 2026 19:48:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408486</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408486</link>
      <description>EUVD-2026-408486</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408486</guid>
    </item>
    <item>
      <title>fkie_cve-2026-110513</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-110513</link>
      <description>&lt;p&gt;Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user&amp;#39;s unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account&amp;#39;s permissions. Only deployments with HTTP enabled are affected.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Iggy: through 0.9.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.10.0, which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user&amp;#39;s unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account&amp;#39;s permissions. Only deployments with HTTP enabled are affected.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Iggy: through 0.9.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.10.0, which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-110513</guid>
    </item>
    <item>
      <title>GHSA-95hx-569q-f3rv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-95hx-569q-f3rv</link>
      <description>&lt;p&gt;Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user&amp;#39;s unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account&amp;#39;s permissions. Only deployments with HTTP enabled are affected.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Iggy: through 0.9.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.10.0, which fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Insufficient Session Expiration vulnerability in the Apache Iggy server HTTP transport. A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID. After an administrator deleted a user, that user&amp;#39;s unexpired token, or a token refreshed from it while the ID was free, authenticated as the next account created with that ID and had that account&amp;#39;s permissions. Only deployments with HTTP enabled are affected.&lt;/p&gt;
&lt;p&gt;This issue affects Apache Iggy: through 0.9.0.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 0.10.0, which fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-95hx-569q-f3rv</guid>
    </item>
  </channel>
</rss>
