# CVE-2026-115824: Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115824, GHSA-frrh-cv34-87px, UBUNTU-CVE-2026-115824

## What is CVE-2026-115824?

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

### Official description

Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies.

The chunked body decoder keeps each chunk in memory until the whole chunk and its CRLF have arrived, and sets no limit on the length of a chunk-size line. A client that declares a huge chunk size and streams data, or sends a chunk-size line that never ends, grows the buffer for as long as it keeps sending.

A remote attacker can exhaust worker memory with a single connection.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115824 is a vulnerability, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115824 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-115824/ (Markdown: https://insights.sbomify.com/CVE-2026-115824/index.md)
```

## Sources

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

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