# CVE-2026-120633: CGI versions before 5.00 for Perl trust the client X-Forwarded-Host header in url, self_url, virtual_host and virtual_port.


- **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-112798, DEBIAN-CVE-2026-120633, DHI-vqbq-iwny-bq5w-zs5x, GHSA-r9xh-qv72-jvjf, UBUNTU-CVE-2026-120633

## What is CVE-2026-120633?

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

### Official description

CGI versions before 5.00 for Perl trust the client X-Forwarded-Host header in url, self_url, virtual_host and virtual_port.

These take the host name and port from the X-Forwarded-Host request header when present, and otherwise from Host, without validating either. The URLs from url and self_url are the default redirect location and the start_html(-base=>1) base href, and the default start_form action when REQUEST_URI is not set.

A client can poison shared caches, and URLs the application stores or sends, with redirects, links and scripts that point at a host it controls.

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-348 (Use of Less Trusted Source)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120633 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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