CVE-2025-40932: GRICHTER Apache::SessionX · Generation of Predictable Numbers or Identifiers
Affects GRICHTER Apache::SessionXSource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GRICHTERApache::SessionX | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should immediately replace the default session ID generator in Apache::SessionX with a cryptographically secure random number generator, such as one based on Perl’s Crypt::Random or similar modules that provide strong entropy sources. Avoid using the built-in rand() function for any security-sensitive operations. If possible, upgrade to a newer version of Apache::SessionX that addresses this issue once available. In the interim, implement additional session security measures such as enforcing HTTPS to protect session IDs in transit, setting secure and HttpOnly flags on cookies, and employing session expiration and regeneration policies to limit session lifetime. Monitor web application logs for suspicious session activity indicative of guessing attempts. Consider deploying web application firewalls (WAFs) to detect and block anomalous session access patterns. Educate developers and administrators about secure session management best practices to prevent similar issues in the future.
Description
Apache::SessionX versions through 2.01 for Perl create insecure session id. Apache::SessionX generates session ids insecurely. The default session id generator in Apache::SessionX::Generate::MD5 returns a MD5 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. Predicable session ids could allow an attacker to gain access to systems.