# CVE-2026-120635: 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.


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** AZL-112762, DEBIAN-CVE-2026-120635, DHI-nrga-z4nf-cfxv-pqtf, GHSA-hc7g-hfjx-mc5f, UBUNTU-CVE-2026-120635

## What is CVE-2026-120635?

CVE-2026-120635 is a high-severity vulnerability, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2026-120635?


## How do I fix CVE-2026-120635?

Upgrade to a fixed version.

## Is CVE-2026-120635 being exploited?

There is no known exploitation of CVE-2026-120635 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120635 and fix it if it is affected.

What it is: CVE-2026-120635 is a high-severity vulnerability, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120635 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120635/ (Markdown: https://insights.sbomify.com/CVE-2026-120635/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120635
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120635
- OSV: https://osv.dev/vulnerability/CVE-2026-120635

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120635/
Summaries are generated and may contain mistakes; the official description above is the record.
