# CVE-2026-115817

> As of 2026-10-25, CVE-2026-115817 is a vulnerability, EPSS 0.3% (22.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-115817 as of 2026-10-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-25

## What is 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. 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.

The record classifies CVE-2026-115817 under weakness class [CWE-770](https://intel.threadlinqs.com/cwe/CWE-770). The identifier was first published 25 days ago.

## Severity and exploitation probability

- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 22.6% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 0.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-25

## Is CVE-2026-115817 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

## Affected products and versions

No affected-product or package list has been recorded for CVE-2026-115817 in the tracked sources. The vendor advisory and the references below are the authoritative statement of what is affected.

## How to fix CVE-2026-115817

Patch reference: [https://github.com/miyagawa/Starman/commit/89dffd3bdc9baa1cbe1b48a43615586ba2588558.patch](https://github.com/miyagawa/Starman/commit/89dffd3bdc9baa1cbe1b48a43615586ba2588558.patch). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-115817

No threat campaign in the Threadlinqs corpus currently references CVE-2026-115817, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, GitHub Security Advisories, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/miyagawa/Starman/commit/89dffd3bdc9baa1cbe1b48a43615586ba2588558.patch)
- [github.com — patch (a30533c03051502d6b67cd48b3a95a61e129691b)](https://github.com/miyagawa/Starman/commit/a30533c03051502d6b67cd48b3a95a61e129691b.patch)
- [metacpan.org — release notes](https://metacpan.org/release/MIYAGAWA/Starman-0.4019/changes)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-115817
No Threadlinqs detection currently covers CVE-2026-115817; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
