Skip to main content

Apache::Session::Generate::ModUniqueId CVE-2026-5081

| EUVD-2026-27823 CRITICAL
Generation of Predictable Numbers or Identifiers (CWE-340)
2026-05-06 CPANSec GHSA-546v-xqjf-qgcr
9.1
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
May 06, 2026 - 16:31 vuln.today
CVSS changed
May 06, 2026 - 15:22 NVD
9.1 (None) 9.1 (CRITICAL)

DescriptionNVD

Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure.

Apache::Session::Generate::ModUniqueId (added in version 1.54) uses the value of the UNIQUE_ID environment variable for the session id. The UNIQUE_ID variable is set by the Apache mod_unique_id plugin, which generates unique ids for the request. The id is based on the IPv4 address, the process id, the epoch time, a 16-bit counter and a thread index, with no obfuscation.

The server IP is often available to the public, and if not available, can be guessed from previous session ids being issued. The process ids may also be guessed from previous session ids. The timestamp is easily guessed (and leaked in the HTTP Date response header).

The purpose of mod_unique_id is to assign a unique id to requests so that events can be correlated in different logs. The id is not designed, nor is it suitable for security purposes.

AnalysisAI

Predictable session ID generation in Apache::Session::Generate::ModUniqueId 1.54-1.94 allows remote unauthenticated attackers to forge session tokens and hijack user sessions. The vulnerability stems from using Apache mod_unique_id values as session identifiers-these values are deterministic and constructed from publicly observable or easily guessable components (server IP, process ID, timestamp, counter). …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Identify all systems running Apache::Session versions 1.54-1.94 and document affected applications; assess whether sessions are actively used for authentication. Within 7 days: Implement session invalidation and force all users to re-authenticate using a different session generation mechanism; review application logs for abnormal session activity or impossible travel patterns indicating hijacking. …

Sign in for detailed remediation steps.

Vendor StatusVendor

Share

CVE-2026-5081 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy