<?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 08:17:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-274123</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-274123</link>
      <description>EUVD-2026-274123</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-274123</guid>
    </item>
    <item>
      <title>fkie_cve-2026-3255</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-3255</link>
      <description>&lt;p&gt;HTTP::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.&lt;/p&gt;
&lt;p&gt;The HTTP::Session2 session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand() function is unsuitable for cryptographic usage.&lt;/p&gt;
&lt;p&gt;HTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;HTTP::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.&lt;/p&gt;
&lt;p&gt;The HTTP::Session2 session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand() function is unsuitable for cryptographic usage.&lt;/p&gt;
&lt;p&gt;HTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-3255</guid>
    </item>
    <item>
      <title>GHSA-2p7f-7xjf-8q9q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2p7f-7xjf-8q9q</link>
      <description>&lt;p&gt;HTTP::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.&lt;/p&gt;
&lt;p&gt;The HTTP::Session2 session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand() function is unsuitable for cryptographic usage.&lt;/p&gt;
&lt;p&gt;HTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;HTTP::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.&lt;/p&gt;
&lt;p&gt;The HTTP::Session2 session id generator returns a SHA-1 hash seeded with the built-in rand function, the epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand() function is unsuitable for cryptographic usage.&lt;/p&gt;
&lt;p&gt;HTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2p7f-7xjf-8q9q</guid>
    </item>
  </channel>
</rss>
