CVE-2026-5081
Apache::Session::Generate::ModUniqueId versions from 1.54 through …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- httpd.apache.org/docs/current/mod/mod_unique_id.html
- metacpan.org/pod/Apache::Session::Generate::Random
- www.openwall.com/lists/oss-security/2026/05/06/6
- access.redhat.com/security/cve/CVE-2026-5081
- bugzilla.redhat.com/show_bug.cgi?id=2467174
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5081.json
- nvd.nist.gov/vuln/detail/CVE-2026-5081
- cve.org/CVERecord?id=CVE-2026-5081
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.