NVD / CVE Program· CNA CPANSec

CVE-2026-93711: Dancer2 versions before 2.2.0 for Perl do not strip CR and LF from response header names in headers_to_array

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: libdancer2-perl (Debian:14) 2.2.2-1; perl-Dancer2 (openSUSE:Tumbleweed) 2.2.2-1.1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to libdancer2-perl (Debian:14) 2.2.2-1; perl-Dancer2 (openSUSE:Tumbleweed) 2.2.2-1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Dancer2 versions before 2.2.0 for Perl do not strip CR and LF from response header names in headers_to_array. The routine removes CR and LF from each header value but not from the name. A name carrying them therefore reaches the PSGI server intact. A server that does not validate keys writes it to the wire, so the bytes after the CRLF arrive as their own header line. The application has to derive the header name from request data, not just the value. An attacker who controls that data adds their own headers and splits the response.

Pre-auth

Published: Sep 21, 2026
Updated: Sep 22, 2026
EPSS: 0.3% · 31th percentile
CWE: CWE-113

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (CPANSec). Independent of NVD's CPE analysis and usually ahead of it.

cpan.org/modules Dancer2
- before 2.2.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	libdancer2-perl	from 0	—
Debian:14	libdancer2-perl	before 2.2.2-1	2.2.2-1
openSUSE:Tumbleweed	perl-Dancer2	before 2.2.2-1.1	2.2.2-1.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:libdancer2-perl	2.2.2-1 · Debian:14	Package registry (OSV)
opensuse:perl-Dancer2	2.2.2-1.1 · openSUSE:Tumbleweed	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.