Response splitting via unsanitized header names
Published Sep 22, 2026 · Updated Sep 22, 2026
HTTP response splitting in PerlDancer Dancer2 before 2.2.0 allows remote attackers to inject response headers through crafted header names. The headers_to_array routine strips CR and LF from each header value but passes header names containing those bytes unchanged into the PSGI header array. Exploitation requires an application to derive a response header name from request data and a PSGI server that does not reject the name, allowing attacker-supplied header lines to reach clients.
Summary
What happened
HTTP response splitting in PerlDancer Dancer2 before 2.2.0 allows remote attackers to inject response headers through crafted header names. The headers_to_array routine strips CR and LF from each header value but passes header names containing those bytes unchanged into the PSGI header array. Exploitation requires an application to derive a response header name from request data and a PSGI server that does not reject the name, allowing attacker-supplied header lines to reach clients.
The record
- CVE
- CVE-2026-93711
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- PerlDancer
- Product
- Dancer2
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started