<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T07:44:49.043635+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2025-40924</id>
    <title>CVE-2025-40924 — Catalyst::Plugin::Session before version 0.44 for Perl generates session ids insecurely</title>
    <updated>2026-10-06T07:44:49.055963+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> HAARG Catalyst::Plugin::Session</p>
<p>Catalyst::Plugin::Session before version 0.44 for Perl generates session ids insecurely.</p>
<p>The session id is generated from a (usually SHA-1) hash of a simple counter, the epoch time, the built-in rand function, the PID and the current Catalyst context. This information is of low entropy. 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.</p>
<p>Predicable session ids could allow an attacker to gain access to systems.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-40924"/>
  </entry>
</feed>
