Live › vulnerability › CVE-2026-116285
Go to dashboardHTTP::Body before 1.23_01 uses a regex to read chunk-size lines in chunked request bodies, and that regex backtracks quadratically on long lines of hex digits without a CR before the LF. A remote attacker can send such a request to make the application spend a lot of CPU, causing denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Perl applications that parse request bodies with HTTP::Body, such as web apps and frameworks built on it, are exposed when they accept chunked request bodies (no Content-Length header). Systems that do not use HTTP::Body, or that reject chunked requests before they reach it, can skip it.
No product ranges from the sources yet.
perl -MHTTP::Body -e 'print $HTTP::Body::VERSION' or cpanm --info HTTP::Bodycpan -l | grep HTTP::Body or your lockfile1.23_01 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
HTTP::Body versions before 1.23_01 for Perl allow CPU exhaustion via quadratic regex backtracking when parsing chunked request bodies.
In chunked mode, used when no content length is given, add() matches each chunk-size line with /^([\da-fA-F]+).*\x0D\x0A/. On a line of hex digits whose first LF has no CR before it, the digits and .* backtrack against each other, so a single add() takes time quadratic in the line's length. Nothing limits how long the line can be.
A remote attacker can exhaust CPU in applications that pass chunked request bodies to HTTP::Body.
This page as .md · .json · in your agent: get_signal("CVE-2026-116285")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.