CVE-2026-5081
Chorny Apache::session::generate::moduniqueid vulnerability
- Published6 May 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/security/cve/CVE-2026-5081
- https://bugzilla.redhat.com/show_bug.cgi?id=2467174
- https://httpd.apache.org/docs/current/mod/mod_unique_id.html
- https://metacpan.org/pod/Apache::Session::Generate::Random
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5081.json
- http://www.openwall.com/lists/oss-security/2026/05/06/6
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-5081 being actively exploited?
CVE-2026-5081 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.
How severe is CVE-2026-5081?
CVE-2026-5081 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.49% probability of exploitation.
Which products are affected by CVE-2026-5081?
Affected products include Chorny Apache::session::generate::moduniqueid.
How do I fix CVE-2026-5081?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-5081 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.