Bug 2467174 (CVE-2026-5081) - CVE-2026-5081 Apache::Session::Generate::ModUniqueId: Perl: mod_unique_id: Apache HTTP Server: Apache::Session::Generate::ModUniqueId: Session ID predictability allows unauthorized access
Summary: CVE-2026-5081 Apache::Session::Generate::ModUniqueId: Perl: mod_unique_id: Ap...
Keywords:
Status: NEW
Alias: CVE-2026-5081
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-06 13:08 UTC by OSIDB Bzimport
Modified: 2026-05-11 05:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-06 13:08:40 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.