Session hijacking via predictable session identifiers
Published Feb 27, 2026 · Updated Feb 27, 2026
Weak session identifier generation in Tokuhiro Matsuno HTTP::Session2 before 1.12 allows remote attackers to predict session IDs. The HTTP::Session2::Random generator hashes Perl rand() output with the process ID, an object address, and the current time when /dev/urandom is unavailable. A reachable application must use the affected generator in fallback mode; a predicted identifier enables session impersonation and access to the victim's session.
Summary
What happened
Weak session identifier generation in Tokuhiro Matsuno HTTP::Session2 before 1.12 allows remote attackers to predict session IDs. The HTTP::Session2::Random generator hashes Perl rand() output with the process ID, an object address, and the current time when /dev/urandom is unavailable. A reachable application must use the affected generator in fallback mode; a predicted identifier enables session impersonation and access to the victim's session.
The record
- CVE
- CVE-2026-3255
- Published
- Feb 27, 2026
- Updated
- Feb 27, 2026
- Vendor
- Tokuhiro Matsuno
- Product
- HTTP::Session2
- Classifications
- CWE-340, CWE-338, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2026CVE publishedPublication date reported by the CVE source.
- Feb 27, 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=0 <1.12
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