# CVE-2026-120648: CGI versions before 5.00 for Perl allow HTML injection via text containing --> in comment


- **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-112783, DEBIAN-CVE-2026-120648, GHSA-v6fq-x7rj-cvvm, UBUNTU-CVE-2026-120648

## What is CVE-2026-120648?

CVE-2026-120648 is a medium-severity vulnerability in CGI, published on 3 Nov 2026. 

### Official description

CGI versions before 5.00 for Perl allow HTML injection via text containing --> in comment.

Arguments are placed between <!-- and --> without escaping, so text containing --> closes the comment early.

An application that passes request data to comment can be made to inject HTML into the page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

1 open source package ship an affected version, including CGI.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `CGI` | cpan | `pkg:cpan/CGI` | All versions | 5.00 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Red Hat | 8 | deferred | `perl-CGI` |  |
| Red Hat | 9 | deferred | `perl-CGI` |  |
| Red Hat | 10 | deferred | `perl-CGI` |  |
| Red Hat | els/7 | deferred | `perl-CGI` |  |

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

Upgrade CGI to 5.00 or later.

## Is CVE-2026-120648 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- CGI (cpan): affected all versions; fixed in 5.00

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-120648/ (Markdown: https://insights.sbomify.com/CVE-2026-120648/index.md)
```

## Sources

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

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