Skip to content
Fencer Vulns
no cvss —

CVE-2026-120650 json

CGI versions before 5.00 for Perl allow memory, CPU and disk exhaustion via missing or unenforced request size, parameter and upload limits

published 2026-11-03 5 d ago modified 2026-11-04 4 d ago also EUVD-2026-116616

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

CGI versions before 5.00 for Perl allow memory, CPU and disk exhaustion via missing or unenforced request size, parameter and upload limits.

$CGI::POST_MAX defaults to no limit, and when set is not enforced for chunked multipart bodies or for the boundary line of a multipart body without a boundary= parameter. Bodies saved as PUTDATA, POSTDATA or PATCHDATA uploads are read into memory in one go, and nothing limits the number of parameters or uploads.

Patch / fix

  • perl-CGI openSUSE Tumbleweed 5.20.0-1.1

opensuse advisories openSUSE-SU-2026:12465-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-120650 updated cvss 7.5

perl-cgi: perl-cgi: Denial of Service via unenforced request and upload limits

  • Red Hat Enterprise Linux 7 perl-CGI 4.61-5.el10 Red Hat Enterprise Linux 8 perl-CGI 4.61-5.el10 Red Hat Enterprise Linux 9 perl-CGI 4.61-5.el10 Red Hat Enterprise Linux 10 perl-CGI 4.61-5.el10
    affected: workaround, no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.