# CVE-2026-5081: Apache::Session::Generate::ModUniqueId versions from 1.54 through 1.94 for Perl session ids are insecure

> Insecure session ID generation in Apache::Session::Generate::ModUniqueId allows attackers to predict session IDs and hijack user sessions.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-5081, GHSA-546v-xqjf-qgcr, UBUNTU-CVE-2026-5081

## What is CVE-2026-5081?

CVE-2026-5081 is a critical vulnerability in CHORNY Apache::Session::Generate::ModUniqueId, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-341 (Predictable from Observable State), CWE-340 (Generation of Predictable Numbers or Identifiers)

## Which versions are affected by CVE-2026-5081?

It affects 1 product.


Products: Chorny Apache\.

## How do I fix CVE-2026-5081?

No fix has been published for CVE-2026-5081 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5081 being exploited?

There is no known exploitation of CVE-2026-5081 in the wild and no public exploit code.

## Other vulnerabilities in CHORNY Apache::Session::Generate::ModUniqueId

- [CVE-2013-10075](https://insights.sbomify.com/CVE-2013-10075/): Apache::Session versions through 1.94 for Perl re-creates deleted sessions (critical 9.1)
- [CVE-2025-40931](https://insights.sbomify.com/CVE-2025-40931/): Apache::Session::Generate::MD5 versions through 1.94 for Perl create insecure session id (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5081 and fix it if it is affected.

What it is: CVE-2026-5081 is a critical vulnerability in CHORNY Apache::Session::Generate::ModUniqueId, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5081 in the wild and no public exploit code.

Affected product: CHORNY Apache::Session::Generate::ModUniqueId. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5081/ (Markdown: https://insights.sbomify.com/CVE-2026-5081/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5081
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5081
- OSV: https://osv.dev/vulnerability/CVE-2026-5081

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5081/
Summaries are generated and may contain mistakes; the official description above is the record.