UBUNTU-CVE-2026-117501: Medium severity ubuntu/libhttp-body-perl vulnerability

Published Nov 3, 2026
·
Updated

HTTP::Body versions before 1.2401 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.

Affected Software

7 affected components
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*
ubuntu/libhttp-body-perl*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade HTTP::Body to a version that resolves this vulnerability.

    Fixed in 1.24_01

Event History

Nov 3, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications using HTTP::Body before 1.24_01 are exposed when they pass chunked HTTP request bodies to the library. Chunked mode is used when the request does not provide a Content-Length header.

2

What does an attacker need to do to trigger memory exhaustion?

A remote attacker must send a chunked request body that causes the parser to wait indefinitely, such as a non-chunk-size line, a chunk-size line without CRLF, or a size too large to fit an integer. Subsequent data supplied through add() is then retained in memory and can exhaust it.

3

Is a Content-Length request affected?

The described unbounded buffering behavior applies to chunked mode, which is used when no Content-Length is given. The provided information does not identify the same behavior for requests with Content-Length.

4

How can I determine whether my deployment is affected?

Check whether the application uses HTTP::Body and whether its version is earlier than 1.24_01. Then determine whether the application passes incoming chunked request bodies to HTTP::Body.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203