# CVE-2026-3256: HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids

> Attackers can predict session IDs due to weak random seeding, potentially leading to account takeover in applications using this Perl library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-mx9c-4xjq-mhj6

## What is CVE-2026-3256?

CVE-2026-3256 is a critical vulnerability in KTAT HTTP::Session, published on 28 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids.

HTTP::Session defaults to using HTTP::Session::ID::SHA1 to generate session ids using a SHA-1 hash seeded with the built-in rand function, the high resolution epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.

The distribution includes HTTP::session::ID::MD5 which contains a similar flaw, but uses the MD5 hash instead.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers), CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

It affects 1 product.


Products: Ktat Http\.

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

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

## Is CVE-2026-3256 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3256 is a critical vulnerability in KTAT HTTP::Session, published on 28 Mar 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-3256 in the wild and no public exploit code.

Affected product: KTAT HTTP::Session. 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-3256/ (Markdown: https://insights.sbomify.com/CVE-2026-3256/index.md)
```

## Sources

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

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