<?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 12:29:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8503 — Apache::Session::Generate::SHA256 versions before 1.3.19 for Perl create insecure session ids</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8503</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; GUIMARD Apache::Session::Generate::SHA256&lt;/p&gt;
&lt;p&gt;Apache::Session::Generate::SHA256 versions before 1.3.19 for Perl create insecure session ids.&lt;/p&gt;
&lt;p&gt;Apache::Session::Generate::SHA256 generated session ids insecurely. The default session id generator returns a SHA-256 hash of the built-in rand() function, the epoch time, and the PID, that is hashed again. These are predictable, low-entropy sources. Predicable session ids could allow an attacker to gain access to systems.&lt;/p&gt;
&lt;p&gt;Note that version 1.3.19 has a fallback without warning to use insecure session generation method if the call to Crypt::URandom::urandom fails. However, this is unlikely as Crypt::URandom is a hardcoded requirement of the module.&lt;/p&gt;
&lt;p&gt;This issue is similar to CVE-2025-40931 for Apache::Session::Generate::MD5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; GUIMARD Apache::Session::Generate::SHA256&lt;/p&gt;
&lt;p&gt;Apache::Session::Generate::SHA256 versions before 1.3.19 for Perl create insecure session ids.&lt;/p&gt;
&lt;p&gt;Apache::Session::Generate::SHA256 generated session ids insecurely. The default session id generator returns a SHA-256 hash of the built-in rand() function, the epoch time, and the PID, that is hashed again. These are predictable, low-entropy sources. Predicable session ids could allow an attacker to gain access to systems.&lt;/p&gt;
&lt;p&gt;Note that version 1.3.19 has a fallback without warning to use insecure session generation method if the call to Crypt::URandom::urandom fails. However, this is unlikely as Crypt::URandom is a hardcoded requirement of the module.&lt;/p&gt;
&lt;p&gt;This issue is similar to CVE-2025-40931 for Apache::Session::Generate::MD5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8503</guid>
    </item>
  </channel>
</rss>
