Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-116131

HTTP::Body versions before 1.23_01 for Perl allow memory and temporary file exhaustion via an unlimited number of form fields and multipart parts

No exploitation reported by the sources we read.

  • Published2026-10-28
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

HTTP::Body versions before 1.23_01 for Perl allow memory and temporary file exhaustion via an unlimited number of form fields and multipart parts. The urlencoded parser splits the whole body on its separators at once, creating one scalar per separator before any field is stored. This costs about 90 bytes of memory per separator byte. The multipart parser creates a temporary file for every part that carries a filename. Neither parser limits how many fields or parts a body may hold. A remote attacker can exhaust worker memory with a body made of separators, or create thousands of temporary files with one request of small file parts.

Timeline

dates in UTC
  1. 2026-10-2817:14CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As CPANSec, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-28

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libhttp-body-perlUbuntu:26.10all versions · no fixed version listed
  • libhttp-body-perlUbuntu:26.04:LTSall versions · no fixed version listed
  • libhttp-body-perlUbuntu:24.04:LTSall versions · no fixed version listed
  • libhttp-body-perlUbuntu:22.04:LTSall versions · no fixed version listed
  • libhttp-body-perlUbuntu:20.04:LTSall versions · no fixed version listed
  • libhttp-body-perlUbuntu:18.04:LTSall versions · no fixed version listed
  • libhttp-body-perlUbuntu:16.04:LTSall versions · no fixed version listed
  • libhttp-body-perlDebian:14all versions · fixed in 1.24.01-1

3 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-116131 Red Hat Product Security

    perl-http-body: HTTP::Body: Denial of Service via unbounded form fields and multipart parts

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Published
2026-10-28
Last Modified
2026-11-05
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-69q5-rpx8-8vpq

Frequently asked questions

What is CVE-2026-116131?

HTTP::Body versions before 1.23_01 for Perl allow memory and temporary file exhaustion via an unlimited number of form fields and multipart parts. The urlencoded parser splits the whole body on its separators at once, creating one scalar per separator before any field is stored. This costs about 90 bytes of memory per separator byte. The multipart parser creates a temporary file for every part that carries a filename. Neither parser limits how many fields or parts a body may hold. A remote attacker can exhaust worker memory with a body made of separators, or create thousands of temporary files with one request of small file parts.

Is CVE-2026-116131 actively exploited?

Active exploitation of CVE-2026-116131 has not been confirmed. Its EPSS score was 0.3% on 2026-11-05, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-116131?

CVE-2026-116131 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Running perl-http-body? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record