CGI header injection in Content-Disposition
Affects CGI for Perl before 5.00 when the header -attachment filename is set. Fixed in CGI 5.00.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.00
- Who is exposed
- Not reported
Summary
The CGI module for Perl (versions before 5.00) is affected. An attacker who can influence the filename passed to the attachment header can inject extra parameters into the Content-Disposition header, which may change the filename a user's browser saves the response under.
Written by a model
Original description
CGI versions before 5.00 for Perl allow Content-Disposition parameter injection via unescaped double quotes in the header attachment filename.
header(-attachment => $name) writes $name into the quoted filename parameter of Content-Disposition without escaping double quotes.
An application that passes request data as the attachment name can be made to send a second filename parameter, changing the name the response is saved under.
What to do
Upgrade to a fixed version: 5.00.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120647 (CGI versions before 5.00 for Perl allow Content-Disposition parameter injection via unescaped double quotes in the header attachment…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120647 (entry last updated 2026-11-09):
Affected:
- CGI: fixed in 5.00
Fixed versions: 5.00.
Conditions (all must be true for the bug to be hit):
- The header -attachment filename is not escaped, so a double quote in the name ends the quoted filename parameter (source: https://github.com/leejo/CGI.pm/commit/131280a5c5bc51b65797bd57ef0ee8da8468065b.patch)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-120647 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120647 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/leejo/CGI.pm/commit/131280a5c5bc51b65797bd57ef0ee8da8468065b.patch
- https://metacpan.org/release/LEEJO/CGI-4.72/source/lib/CGI.pm
- https://metacpan.org/release/LEEJO/CGI-5.00/changes
- https://www.cve.org/CVERecord?id=CVE-2026-120647
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120647
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120647"}.Affected versions
- CGIfixed in 5.00
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now6 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.61%
- Posted on X by cve.now Nov 9
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-120647 |
| Record | NVD · CVE-2026-120647 |
| Other links 3 | |
| Patch | GitHub · leejo/CGI.pm · Commit 131280a5 |
| Link | metacpan.org · release/LEEJO/CGI-4.72/source/lib/CGI.pm |
| Link | metacpan.org · release/LEEJO/CGI-5.00/changes |
Questions about CVE-2026-120647
Is CVE-2026-120647 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
What does this mean?
A double quote in the attachment filename is not escaped, so it ends the quoted filename parameter early and lets an attacker inject extra parameters into the Content-Disposition header.
Source: github.com, cve.org
Which versions are affected by CVE-2026-120647?
CGI: before 5.00.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of CGI for Perl before 5.00 are affected, but only in setups that pass a filename to the header -attachment option. Check the installed CGI module version to see which release you have.
Source: github.com, cve.org
How do I fix CVE-2026-120647?
Upgrade CGI to version 5.00 or later, which fixes the issue.
Source: github.com, cve.org
Related
- CVE-2026-63411Jane: Instantiation RCE via parameter description -> raw PHPDoc */ breakout (jane-php/open-api-3)
- CVE-2026-63412Jane: Instantiation RCE via query parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
- CVE-2026-87789AppleScript Code Injection in LVRTC eParakstītājs 3.0
- CVE-2026-76090Tapir: Construction/decode RCE via property name -> raw case-class field (tapir-openapi-codegen)
- CVE-2026-131055Improper output encoding in Editing in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to…
- CVE-2026-130234Path Parameter Encoding in Okta Swift Management SDK
No corrections so far. Something wrong on this page? Report an error.