# CVE-2026-115817: Starman versions before 0.4019 for Perl allow a stalled request body to hold a worker indefinitely, as read_timeout covers only the headers.


- **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-115817, GHSA-xcqf-6xfj-3q3x, UBUNTU-CVE-2026-115817

## What is CVE-2026-115817?

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

### Official description

Starman versions before 0.4019 for Perl allow a stalled request body to hold a worker indefinitely, as read_timeout covers only the headers.

Content-Length and chunked request bodies are read with blocking reads and no deadline. A client that sends complete headers and then stalls or trickles the body keeps the worker waiting until it disconnects.

A remote attacker can take every worker with a few such connections, five with the default worker count, so the server stops answering requests.

Version 0.4019 applies read_timeout to each wait for body data and adds a body_timeout limit, 300 seconds by default, on the total time to read a body.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-115817 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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