# CVE-2025-15578: Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely

> Insecure session ID generation in Maypole allows attackers to predict session IDs and hijack user accounts.

- **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:** 16 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-m76j-7jh6-jxj5

## What is CVE-2025-15578?

CVE-2025-15578 is a critical vulnerability in TEEJAY Maypole, published on 16 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely. The session id is seeded with the system time (which is available from HTTP response headers), a call to the built-in rand() function, and the PID.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2025-15578?

It affects 1 product.


Products: Teejay Maypole.

## How do I fix CVE-2025-15578?

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

## Is CVE-2025-15578 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15578 and fix it if it is affected.

What it is: CVE-2025-15578 is a critical vulnerability in TEEJAY Maypole, published on 16 Feb 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-2025-15578 in the wild and no public exploit code.

Affected product: TEEJAY Maypole. 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-2025-15578/ (Markdown: https://insights.sbomify.com/CVE-2025-15578/index.md)
```

## Sources

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

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