cve.bz

CVE-2026-115817

7.5 highEPSS 0.5%

High (7.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-115817 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115817?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115817?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115817 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13starmanno fix listedDEBIAN-CVE-2026-115817
Debian14starman0.4019-1DEBIAN-CVE-2026-115817
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morestarmanno fix listedUBUNTU-CVE-2026-115817
openSUSETumbleweedperl-Starman0.4019-1.1openSUSE-SU-2026:12276-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Starman before 0.4019 reads request bodies (both Content-Length and chunked) with blocking reads and no deadline; read_timeout applied only to headers. A remote, unauthenticated attacker can send complete headers and then stall or trickle the body, holding a worker until disconnect; with the default 5 workers, a few such connections exhaust all workers, causing denial of service. A buffering reverse proxy in front of Starman mitigates exposure. Fixed in 0.4019: read_timeout now applies to each body-data wait and the new body_timeout (default 300s) bounds total body read time; expiry returns 408.

Red Hat's mitigation

Upgrade Starman to 0.4019 or later. As a workaround, place a buffering reverse proxy in front of Starman and limit concurrent connections; on fixed versions, tune --read-timeout/--body-timeout as needed.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115817.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON