VulnerabilityPublished 25 Oct 2026Updated 28 Oct 2026

CVE-2026-115817: Starman versions before 0.4019 for Perl allow a stalled request body to hold a worker indefinitely

Affects starmanSource GCVE Database

Authoritative record:CVE-2026-115817· High

Not known to be exploited.

Data as of 28 Oct 2026, 22:31 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10starman`pkg:deb/ubuntu/starman?arch=source&distro=stonking`Other threats	Affected =0.4017-1build1 =0.4018-1	Fixed in–
Ubuntu 26.04 LTSstarman`pkg:deb/ubuntu/starman?arch=source&distro=resolute`Other threats	Affected =0.4017-1 =0.4017-1build1	Fixed in–
Ubuntu 24.04 LTSstarman`pkg:deb/ubuntu/starman?arch=source&distro=noble`Other threats	Affected =0.4016-1 =0.4017-1	Fixed in–
Ubuntu 22.04 LTSstarman`pkg:deb/ubuntu/starman?arch=source&distro=jammy`Other threats	Affected =0.4015-1	Fixed in–
Ubuntu 20.04 LTSstarman`pkg:deb/ubuntu/starman?arch=source&distro=focal`Other threats	Affected =0.4014-3 =0.4015-1	Fixed in–
Ubuntu 18.04 LTSstarman`pkg:deb/ubuntu/starman?arch=source&distro=bionic`Other threats	Affected =0.4014-1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…