- Exploited
- No known exploitation
- Fix
- Fixed in 1.24_02
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.24_02.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.20% · 10th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HTTP::Body for Perl, in versions before 1.24_02, can be made to parse request trailers in quadratic time, so a remote attacker can use a single request to exhaust the server's CPU. The attack requires no login, and the issue is fixed in version 1.25, which limits the size and number of trailer lines.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
HTTP::Body versions before 1.24_02 for Perl parse the trailer in quadratic time.
Everything after the last chunk in the same call to add() is parsed with HTTP::Headers, which takes time quadratic in the number of fields of one name. For example, it takes several seconds to parse 16 KiB of "a:" lines.
A remote attackercan exhause the CPU with a single request.
HTTP::Body version 1.25 limits the size and number of lines in the trailer.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.24_02.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- HTTP-Body
fixed in 1.24_02
Evidence 3
- Patch
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121006
Is CVE-2026-121006 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121006?
HTTP-Body: before 1.24_02.Source: cve.now feed data
How do I fix CVE-2026-121006?
Upgrade to a fixed version: 1.24_02.Source: cve.now feed data