<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T18:06:58.806127+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-8503</id>
    <title>CVE-2026-8503 — Apache::Session::Generate::SHA256 versions before 1.3.19 for Perl create insecure session ids</title>
    <updated>2026-10-06T18:06:58.827247+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> GUIMARD Apache::Session::Generate::SHA256</p>
<p>Apache::Session::Generate::SHA256 versions before 1.3.19 for Perl create insecure session ids.</p>
<p>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.</p>
<p>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.</p>
<p>This issue is similar to CVE-2025-40931 for Apache::Session::Generate::MD5.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-8503"/>
  </entry>
</feed>
