# CVE-2026-120636: CGI versions before 5.00 for Perl allow open redirects and script injection via URLs built from REQUEST_URI in url and start_form.


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** AZL-112765, DEBIAN-CVE-2026-120636, DHI-bjd4-t2qy-rpbs-vant, GHSA-7432-xjrv-h264, UBUNTU-CVE-2026-120636

## What is CVE-2026-120636?

CVE-2026-120636 is a medium-severity vulnerability, published on 3 Nov 2026. 

### Official description

CGI versions before 5.00 for Perl allow open redirects and script injection via URLs built from REQUEST_URI in url and start_form.

url(-absolute=>1), url(-relative=>1) and the default start_form action are built from the client-supplied REQUEST_URI without validation. The result can be protocol-relative (//evil.example), absolute-form (http://evil.example/) or contain backslashes, and url(-relative=>1) can return a javascript: URL. Links and form posts built from these URLs can go to another host.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-601 (URL Redirection to Untrusted Site)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120636 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120636 is a medium-severity vulnerability, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120636 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-120636/ (Markdown: https://insights.sbomify.com/CVE-2026-120636/index.md)
```

## Sources

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

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