Quick answers
- Is CVE-2026-120650 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120650 being exploited in the wild.
- How severe is CVE-2026-120650?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Perl CGI before 5.00.
- Is there a fix for CVE-2026-120650?
- Yes: fixed in CGI 5.00. Until then: Set $CGI::POST_MAX to a finite value appropriate for your application and enforce limits on the number of parameters and uploads; alternatively, restrict POST request body sizes at the web server or reverse proxy level. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120650 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120650?
- Check whether you run Perl CGI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: CGI 5.00
Set $CGI::POST_MAX to a finite value appropriate for your application and enforce limits on the number of parameters and uploads; alternatively, restrict POST request body sizes at the web server or reverse proxy level.
Technical details
The CGI library fails to enforce limits on POST request bodies, multipart parameters, and file uploads. The $CGI::POST_MAX variable defaults to unlimited and is not enforced for chunked multipart bodies or boundary lines; bodies are read entirely into memory in a single operation without size constraints. An attacker can send requests with unbounded body sizes or parameter counts over the network, triggering memory exhaustion and denial of service.
Affected products
- Perl CGI before 5.00
Timeline
- 2026-11-04: disclosed