VulnerabilityPublished 6 Nov 2026

CVE-2026-121006: HTTP-Body (Perl module) · Unthrottled Resource Allocation

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

Compare

Not known to be exploited : upgrade to 1.24_02 soon.

Data as of 6 Nov 2026, 08:05 UTC

Severity

High

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

Thin evidence

One scorer or none

Patch: Available – fixed in 1.24_02

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.24_02.

Affected software

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

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

AI-suggested

Upgrade HTTP::Body to version 1.24_02 or later, as this version fixes the vulnerability. Version 1.25 additionally limits the size and number of lines in the trailer, providing further protection. No other mitigation is indicated.

Description

CVE-2026-121006 is a vulnerability in HTTP::Body for Perl versions before 1.24_02 where parsing the trailer section of an HTTP request occurs in quadratic time. This inefficiency arises because the trailer is parsed with HTTP::Headers, which takes time quadratic in the number of repeated header fields. An attacker can exploit this by sending a single request with many repeated trailer fields, causing excessive CPU usage. Version 1.25 of HTTP::Body addresses this by limiting the size and number of lines in the trailer.

Impact

A remote attacker can cause a denial of service by exhausting the CPU of a system running vulnerable versions of HTTP::Body through a single specially crafted HTTP request containing many repeated trailer fields. This leads to high CPU consumption and potential service disruption.

Summary

HTTP::Body versions prior to 1.24_02 parse the trailer portion of HTTP requests inefficiently, resulting in quadratic time complexity when processing repeated header fields in the trailer. Specifically, all data after the last chunk is parsed by HTTP::Headers, which performs poorly when many fields share the same name. This can be exploited remotely by an attacker to exhaust CPU resources with a single crafted request. The issue is fixed starting with version 1.24_02, and version 1.25 further improves mitigation by limiting trailer size and line count.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (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 6 Nov 2026, 08:05 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats