CVE-2026-115824

Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies

Published Oct 25, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies.

The chunked body decoder keeps each chunk in memory until the whole chunk and its CRLF have arrived, and sets no limit on the length of a chunk-size line. A client that declares a huge chunk size and streams data, or sends a chunk-size line that never ends, grows the buffer for as long as it keeps sending.

A remote attacker can exhaust worker memory with a single connection.

Analysis

AI-generated

Technical impact

Starman versions before 0.4019 contain a flaw in the chunked request decoder that buffers each complete chunk in memory until the chunk and its CRLF are fully received, and the decoder imposes no limit on the length of the chunk-size line. Because of this, a client that reports an extremely large chunk size or sends a chunk-size line that never terminates can cause the server to allocate memory continuously as the data streams in. This unbounded allocation can consume all memory available to a worker process, rendering the application unresponsive and resulting in a denial‑of‑service condition.

Affected Systems

The vulnerability affects the Starman Perl application server in all releases earlier than 0.4019. Users running Starman 0.4019 or later are not impacted. The vendor is MIYAGAWA, and the flaw resides in the Starman package’s implementation of HTTP chunked transfer decoding.

Risk and Exploitability

A remote attacker can trigger the memory exhaustion with a single TCP connection by sending a malicious chunked request. The CVSS score of 7.5 indicates a high severity, and the EPSS score of <1% suggests a low probability of exploitation, while the vulnerability is not listed in the CISA KEV catalog. Because the exploit requires only a single malformed request, the risk of denial of service remains significant for systems that expose Starman to external traffic.

Remediation

Vendor Solution

Upgrade to Starman 0.4019 or later.


OpenCVE Recommended Actions

  • Upgrade to Starman 0.4019 or later to remove the unbounded buffering logic.
  • Configure any front‑end proxy or load balancer to reject or throttle chunked requests that contain unusually large chunk sizes or missing terminating CRLFs.
  • Implement runtime monitoring of worker process memory usage and set up automatic restarts or fail‑over mechanisms to mitigate any lingering denial‑of‑service risk.

Generated by OpenCVE AI on October 29, 2026 at 13:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Miyagawa
Miyagawa starman
Vendors & Products Miyagawa
Miyagawa starman
Type Values Removed Values Added
Description Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies. The chunked body decoder keeps each chunk in memory until the whole chunk and its CRLF have arrived, and sets no limit on the length of a chunk-size line. A client that declares a huge chunk size and streams data, or sends a chunk-size line that never ends, grows the buffer for as long as it keeps sending. A remote attacker can exhaust worker memory with a single connection.
Title Starman versions before 0.4019 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies
Weaknesses CWE-770
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 2, 2026, 4:17 PM
Reserved
Oct 23, 2026, 4:47 PM
Status
Deferred
Published
Oct 25, 2026, 5:17 PM
Modified
Nov 2, 2026, 5:17 PM
Severity
Important
Public date
Oct 25, 2026, 4:51 PM