Session hijacking via predictable session identifiers
Published Feb 16, 2026 · Updated Feb 16, 2026
Weak session ID generation in Maypole 2.10 through 2.13 allows remote attackers to hijack authenticated sessions via predicted identifiers. Maypole::Session seeds Perl's rand() with the system time and process ID, producing identifiers from attacker-estimable inputs rather than cryptographic entropy. Exploitation requires observing the server time and predicting the remaining generator state; a successful guess impersonates the authenticated session bound to that identifier.
Summary
What happened
Weak session ID generation in Maypole 2.10 through 2.13 allows remote attackers to hijack authenticated sessions via predicted identifiers. Maypole::Session seeds Perl's rand() with the system time and process ID, producing identifiers from attacker-estimable inputs rather than cryptographic entropy. Exploitation requires observing the server time and predicting the remaining generator state; a successful guess impersonates the authenticated session bound to that identifier.
The record
- CVE
- CVE-2025-15578
- Published
- Feb 16, 2026
- Updated
- Feb 16, 2026
- Vendor
- Aaron James Trevena
- Product
- Maypole
- Classifications
- CWE-338, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2026CVE publishedPublication date reported by the CVE source.
- Feb 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.10 <=2.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo