Skip to main content
← Vulnerabilities

CGI versions before 5.00 for Perl allow an infinite loop on a short request body when $DISABLE_UPLOADS is set

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 5.00
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.00.

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity?/10Severity: unknown (data gap). 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

CVE-2026-120651 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects CGI; fixed in 5.00.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Fix
Fixed in 5.00
None on Exploit-DB, Metasploit or GitHub

Summary

The CGI module for Perl, in versions before 5.00, is affected when the DISABLE_UPLOADS option is enabled. A single request with a body shorter than its declared Content-Length can make the server process loop forever, tying up the process and potentially causing a denial of service.

Read the original description

CGI versions before 5.00 for Perl allow an infinite loop on a short request body when $DISABLE_UPLOADS is set. When $CGI::PUTDATA_UPLOAD or an upload hook is set, read_postdata_putdata takes a request body that is not a form submission. With $CGI::DISABLE_UPLOADS set, it discards the body by reading until Content-Length bytes have arrived. Once a body shorter than its Content-Length runs out, every read returns 0, so the loop never ends. A client can keep a server process spinning with one such request.

What to do

  • Upgrade to a fixed version: 5.00.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • CGI

    fixed in 5.00

Evidence 4

  1. Patch
  2. Patch
  3. Link
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120651

Is CVE-2026-120651 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-120651?

CGI: before 5.00.Source: cve.now feed data

How do I fix CVE-2026-120651?

Upgrade to a fixed version: 5.00.Source: cve.now feed data