VulnerabilityPublished 28 Oct 2026

CVE-2026-116531: HTTP-Body (Perl module) · Improper Handling of Length Parameter Inconsistency

Affects HTTP-Body (Perl module)Source CVE Database V5

Not known to be exploited : upgrade to 1.23_01 soon.

Data as of 28 Oct 2026, 17:45 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 1.23_01

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade HTTP-Body (Perl module) to 1.23_01.

Affected software

Product	Affected	Fixed in
HTTP-Body	Affected <1.23_01	Fixed in 1.23_01
CPANHTTP-Body`pkg:cpan/HTTP-Body`Other threats	Affected <1.23_01	Fixed in 1.23_01

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available in HTTP::Body version 1.23_01. Users should upgrade to version 1.23_01 or later to remediate this issue.

Description

HTTP::Body versions before 1.23_01 for Perl improperly handle chunked HTTP request bodies, losing track of chunk boundaries when a read ends inside a chunk. This can cause a server to hang indefinitely or prematurely consider a chunked body complete, potentially misinterpreting leftover bytes as a new request.

Impact

A remote attacker can exploit this vulnerability to cause a denial of service by making a server hang indefinitely while reading a chunked request body. Additionally, the attacker may cause the server to prematurely consider the chunked body complete, potentially leading to misinterpretation of subsequent data as a new request, which could disrupt normal server operation or request processing.

Summary

The vulnerability in HTTP::Body versions prior to 1.23_01 arises from improper handling of length parameters in chunked HTTP request bodies. Specifically, when reading chunked data without a content length, the add() function incorrectly treats a chunk as complete once the buffer length matches the declared chunk size, even if the buffer still contains the chunk-size line. If a read ends within the last bytes of a chunk, add() prematurely finalizes the chunk and misparses leftover data as the next chunk-size line. This flaw allows a remote attacker to craft chunked bodies that either never complete, causing a server to hang while waiting for the body to finish, or complete early, leaving residual bytes to be interpreted as a subsequent request.

CWE-130Improper Handling of Length Parameter Inconsistency (opens in a new tab)
Base weakness
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
Implementation
When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
Implementation
Do not let the user control the size of the buffer.
Implementation
Validate that the length of the user-supplied data is consistent with the buffer size.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Parameter Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 17:45 UTC

WeaknessesCWE-130

Technical details

References

Community reviews

Related threats