Skip to main content
← Vulnerabilities

CGI versions before 5.00 for Perl allow form fields to be smuggled past proxies and WAFs via multipart parsing that differs from the RFCs

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-120635 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. Attackers can craft multipart form submissions that the module parses differently than security proxies and web application firewalls do, letting malicious form fields slip past those defenses.

Read the original description

CGI versions before 5.00 for Perl allow form fields to be smuggled past proxies and WAFs via multipart parsing that differs from the RFCs. The multipart/form-data parser matches the boundary anywhere rather than at the start of a line, uses the boundary without its leading -- for some client-supplied User-Agent values, finds the Content-Disposition name and filename inside the quoted values of other parameters, and corrupts parts when the boundary nears the 4096-byte read size.

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 7

  1. Patch
  2. Patch
  3. Patch
  4. Patch
  5. Link
Show all 7 sourcesShow fewer sources
  1. Link
  2. Link

Corrections

None so far.

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

FAQ

Questions about CVE-2026-120635

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

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

How do I fix CVE-2026-120635?

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