# CVE-2026-115823: Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections.


- **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-115823, GHSA-4q75-5w63-6hx7, UBUNTU-CVE-2026-115823

## What is CVE-2026-115823?

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

### Official description

Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections.

For a HEAD request Starman omits chunked framing but still writes the body returned by the application, on both the array and streaming response paths. Responses with a 1xx, 204 or 304 status also carry the body.

On a keep-alive or pipelined connection the client reads those bytes as the start of the next response. A front-end proxy that reuses upstream connections may then pair responses with the wrong requests.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115823 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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