CVE-2026-5080: CWE-340 Generation of Predictable Numbers or Identifiers in BIGPRESH Dancer::Session::Abstract
Dancer::Session::Abstract versions through 1.3522 for Perl generates session ids insecurely. The session id is generated from summing the character codepoints of the absolute pathname with the process id, the epoch time and calls to the built-in rand() function to return a number between 0 and 999-billion, and concatenating that result three times. The path name might be known or guessed by an attacker, especially for applications known to be written using Dancer with standard installation locations. The epoch time can be guessed by an attacker, and may be leaked in the HTTP header. The process id comes from a small set of numbers, and workers may have sequential process ids. The built-in rand() function is seeded with 32-bits and is considered unsuitable for security applications. Predictable session ids could allow an attacker to gain access to systems.
AI Analysis
Technical Summary
The vulnerability in Dancer::Session::Abstract (CVE-2026-5080) arises from insecure session ID generation. The session ID is created by summing character codepoints of the absolute pathname, process ID, epoch time, and calls to Perl's built-in rand() function, then concatenating the result three times. Because the pathname may be known or guessed, the epoch time can be inferred or leaked, and the process ID is from a limited set, the resulting session IDs are predictable. Additionally, the rand() function is seeded with only 32 bits and is not suitable for cryptographic security. This predictability violates CWE-340 and CWE-338, potentially allowing attackers to guess valid session IDs and gain unauthorized access.
Potential Impact
Predictable session IDs can lead to session fixation or session hijacking attacks, enabling unauthorized users to impersonate legitimate users or access protected resources. The insecure generation method compromises the confidentiality and integrity of sessions managed by Dancer::Session::Abstract versions through 1.3522.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing alternative secure session ID generation methods that use cryptographically secure random number generators. Avoid relying on the built-in rand() function for security-sensitive identifiers.
CVE-2026-5080: CWE-340 Generation of Predictable Numbers or Identifiers in BIGPRESH Dancer::Session::Abstract
Description
Dancer::Session::Abstract versions through 1.3522 for Perl generates session ids insecurely. The session id is generated from summing the character codepoints of the absolute pathname with the process id, the epoch time and calls to the built-in rand() function to return a number between 0 and 999-billion, and concatenating that result three times. The path name might be known or guessed by an attacker, especially for applications known to be written using Dancer with standard installation locations. The epoch time can be guessed by an attacker, and may be leaked in the HTTP header. The process id comes from a small set of numbers, and workers may have sequential process ids. The built-in rand() function is seeded with 32-bits and is considered unsuitable for security applications. Predictable session ids could allow an attacker to gain access to systems.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Dancer::Session::Abstract (CVE-2026-5080) arises from insecure session ID generation. The session ID is created by summing character codepoints of the absolute pathname, process ID, epoch time, and calls to Perl's built-in rand() function, then concatenating the result three times. Because the pathname may be known or guessed, the epoch time can be inferred or leaked, and the process ID is from a limited set, the resulting session IDs are predictable. Additionally, the rand() function is seeded with only 32 bits and is not suitable for cryptographic security. This predictability violates CWE-340 and CWE-338, potentially allowing attackers to guess valid session IDs and gain unauthorized access.
Potential Impact
Predictable session IDs can lead to session fixation or session hijacking attacks, enabling unauthorized users to impersonate legitimate users or access protected resources. The insecure generation method compromises the confidentiality and integrity of sessions managed by Dancer::Session::Abstract versions through 1.3522.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing alternative secure session ID generation methods that use cryptographically secure random number generators. Avoid relying on the built-in rand() function for security-sensitive identifiers.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-03-28T19:06:14.484Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f3499ecbff5d8610da76f7
Added to database: 4/30/2026, 12:22:54 PM
Last enriched: 4/30/2026, 12:36:27 PM
Last updated: 4/30/2026, 2:23:34 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.