# CVE-2026-115825: HTTP::Server::PSGI versions before 1.0056 for Perl allow a single request to crash the server by declaring a large Content-Length.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115825, GHSA-jmh5-fmfv-h6f8

## What is CVE-2026-115825?

CVE-2026-115825 is a vulnerability, published on 25 Oct 2026. 

### Official description

HTTP::Server::PSGI versions before 1.0056 for Perl allow a single request to crash the server by declaring a large Content-Length.

The request body is read with sysread() calls sized by the remaining Content-Length. Perl grows the read buffer to the requested length before any data arrives, so the server tries to allocate as much memory as the client declares.

A remote attacker can send one request with a large Content-Length and a few body bytes, and perl exits with an out-of-memory error before the application is called. HTTP::Server::PSGI runs as a single process, so the server stays down until restarted.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115825 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115825 is a vulnerability, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115825 in the wild and no public exploit code.

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-115825/ (Markdown: https://insights.sbomify.com/CVE-2026-115825/index.md)
```

## Sources

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

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