CVE-2026-117501

HTTP::Body versions before 1.24_01 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies

Published Oct 28, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
HTTP::Body versions before 1.24_01 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies.

In chunked mode, used when no content length is given, add() holds each chunk in memory until all of it has arrived. A line that is not a chunk-size line, a size line without CRLF, or a size too large to fit an integer leaves the parser waiting forever, and every later add() grows the buffer.

A remote attacker can exhaust memory in applications that pass chunked request bodies to HTTP::Body.

Analysis

AI-generated

Technical impact

The vulnerability exists in HTTP::Body modules older than version 1.24_01. In chunked request processing, each chunk is kept in memory until the complete body is received. A malformed chunk—such as missing CRLF, an invalid size line, or a size that is too large for an integer—causes the parser to wait indefinitely. Subsequent add() calls continue to grow the buffer, eventually exhausting the process memory and leading to denial of service for applications that rely on HTTP::Body to handle incoming request bodies.

Affected Systems

Applications written in Perl that depend on HTTP::Body 1.23.x or earlier are affected. The fix requires upgrading the module to 1.24_01 or later. No specific version list beyond "before 1.24_01" is provided, but any instance using an older release that processes chunked request bodies is vulnerable.

Risk and Exploitability

A remote attacker can exploit this flaw by sending a specially crafted HTTP request with chunked transfer encoding to a vulnerable server. The EPSS score is 0.0024 (< 1%) and the issue is not listed in CISA KEV, so the likelihood of exploitation is unclear, but memory exhaustion can cause a denial‑of‑service that affects application availability. The CVSS score is 7.5, so the vulnerability is considered high severity.

Remediation

Vendor Solution

Upgrade to HTTP-Body 1.24_01 or later.


OpenCVE Recommended Actions

  • Upgrade HTTP::Body to version 1.24_01 or newer to remove the unbounded buffering bug.
  • Configure the application to validate or reject excessively large or malformed chunked request bodies, for example by setting a maximum body size or timeout.
  • Implement a monitoring mechanism to detect memory usage spikes and trigger a graceful restart or shutdown of the affected application.

Generated by OpenCVE AI on October 31, 2026 at 01:52 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 Libwww-perl
Libwww-perl http-body
Vendors & Products Libwww-perl
Libwww-perl http-body
Type Values Removed Values Added
Description HTTP::Body versions before 1.24_01 for Perl allow memory exhaustion via unbounded buffering of chunked request bodies. In chunked mode, used when no content length is given, add() holds each chunk in memory until all of it has arrived. A line that is not a chunk-size line, a size line without CRLF, or a size too large to fit an integer leaves the parser waiting forever, and every later add() grows the buffer. A remote attacker can exhaust memory in applications that pass chunked request bodies to HTTP::Body.
Title HTTP::Body versions before 1.24_01 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 5, 2026, 9:04 PM
Reserved
Oct 27, 2026, 8:44 AM
Status
Awaiting Analysis
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 5, 2026, 9:18 PM
Severity
Important
Public date
Oct 28, 2026, 5:17 PM