Live › vulnerability › CVE-2026-116531
Go to dashboardHTTP::Body for Perl mishandles chunk boundaries in chunked request bodies when a read ends inside a chunk. A remote attacker can make a body never complete, hanging a server, or make it complete early so leftover bytes are parsed as a second request.
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 chunked request bodies with HTTP::Body, typically through a web framework or server that uses it for request parsing. Requests without a Content-Length header take the chunked path. Applications that do not use HTTP::Body for request bodies are unlikely to be affected; the sources do not say more.
No product ranges from the sources yet.
perl -MHTTP::Body -e 'print $HTTP::Body::VERSION'1.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 lose track of chunk boundaries in chunked request bodies when a read ends inside a chunk.
In chunked mode, used when no content length is given, add() treats a chunk as complete once the buffer is as long as the chunk's declared size, but the buffer still holds the chunk-size line. When a read ends in the last bytes of a chunk, add() takes the chunk short and parses the leftover data as the next chunk-size line.
A remote attacker can make a chunked body never complete, hanging a server that reads until the body is done, and may make it complete early, leaving the remaining bytes to be read as the next request.
This page as .md · .json · in your agent: get_signal("CVE-2026-116531")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.