CVE-2026-120650

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

publishedCWE-770

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.

Technical severityUnscoredNo score in collected sources

Published2026-11-03Source updated 2026-11-03

Collected2026-11-041 attributed source

Fixes and workarounds

Fix

Upgrade to CGI 5.00 or later.

Source: CNA: CPANSec

Workaround

For deployments that cannot upgrade, limit the request body size at the web server and set $CGI::POST_MAX.

Source: CNA: CPANSec

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: CPANSec

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: CPANSec

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: CPANSec

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: CPANSec

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
`CGI` cpan	≥ 0; < 5.00 (affected, custom) Other versions: unaffected	CNA: CPANSec

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

No CVSS assessment reported. An unscored record is not a low-severity determination.

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

https://metacpan.org/release/LEEJO/CGI-4.72/source/lib/CGI.pmCNA: CPANSec · technical-description
https://metacpan.org/release/LEEJO/CGI-5.00/changesCNA: CPANSec · release-notes
https://github.com/leejo/CGI.pm/commit/17b838dc14d2b82ae6c7e76f66ec2c3f3b08038b.patchCNA: CPANSec · patch
https://github.com/leejo/CGI.pm/commit/f3febefe63fe3881d8c3ae10fa83ca8ec950b959.patchCNA: CPANSec · patch
https://github.com/leejo/CGI.pm/commit/277baeb74fde7bce975a7bd0a1f98dcf1b9b2050.patchCNA: CPANSec · patch
https://github.com/leejo/CGI.pm/commit/8940a74e53a41563f72813b45f99cceaaa4c92e8.patchCNA: CPANSec · patch

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide