CVE-2026-115865

Starlet versions before 0.33 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory

Published Oct 30, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Starlet versions before 0.33 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory.

The request body is read in a loop that asks sysread for all of the remaining declared length at once. Perl grows the read buffer to that size before any data arrives, so a length larger than available memory makes the worker exit with an uncatchable out of memory error before the application is called.

A remote attacker can force a worker restart with each request of a few bytes.

Analysis

AI-generated

Technical impact

Starlet versions before 0.33 expose a flaw where a request that declares a large Content‑Length header forces the Perl runtime to pre‑allocate a buffer equal to that length. If the declared length exceeds available memory, the worker process dies with an uncaught out‑of‑memory exception before any application code runs, resulting in a service restart. The vulnerability can be triggered with a very small request body; the attacker simply repeats the exploit to cause repeated worker restarts,

Affected Systems

This issue affects the Starlet Perl module in all releases older than 0.33. Systems running code that imports Starlet for HTTP server capabilities and that accept externally supplied Content‑Length headers are potentially impacted. The specific versions are any Starlet version earlier than 0.33.

Risk and Exploitability

The flaw is exploitable over the network, requiring no special privileges and allowing an attacker to cause a denial of service simply by sending specially crafted HTTP requests. The CVSS score is 7.5 and the EPSS score is < 1%, and the vulnerability is not listed in CISA KEV catalog, but the consequence is a forced restart of worker processes which can incapacitate the entire application or service until the workers recover. The attack vector is remote over HTTP and can be performed repeatedly, leading to sustained availability loss.

Remediation

Vendor Solution

Upgrade to Starlet 0.33 or later.


OpenCVE Recommended Actions

  • Upgrade to Starlet 0.33 or later
  • Restart all affected services so the new binaries are in use
  • Configure server limits to cap maximum Content‑Length values to mitigate while waiting for updates

Generated by OpenCVE AI on November 4, 2026 at 07:27 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
Weaknesses CWE-770
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 Kazuho
Kazuho starlet
Vendors & Products Kazuho
Kazuho starlet
Type Values Removed Values Added
Description Starlet versions before 0.33 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory. The request body is read in a loop that asks sysread for all of the remaining declared length at once. Perl grows the read buffer to that size before any data arrives, so a length larger than available memory makes the worker exit with an uncatchable out of memory error before the application is called. A remote attacker can force a worker restart with each request of a few bytes.
Title Starlet versions before 0.33 for Perl allow a request declaring a large Content-Length to kill a worker by exhausting memory
Weaknesses CWE-789
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 6, 2026, 4:42 PM
Reserved
Oct 23, 2026, 5:37 PM
Status
Deferred
Published
Oct 30, 2026, 1:18 PM
Modified
Nov 6, 2026, 5:17 PM
Severity
Important
Public date
Oct 30, 2026, 12:44 PM