CVE-2026-93711 Affecting libdancer2-perl package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LIBDANCER2PERL-20044316
- published22 Sept 2026
- disclosed22 Sept 2026
Introduced: 22 Sep 2026
NewCVE-2026-93711 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest libdancer2-perl.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libdancer2-perl package and not the libdancer2-perl package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.
References
- https://advisory.echohq.com/cve/CVE-2026-93711
- https://github.com/PerlDancer/Dancer2/commit/ff89ac12af7b8899812a79e9924dfea7a5d9833b.patch
- https://github.com/PerlDancer/Dancer2/issues/1822
- https://metacpan.org/release/CROMEDOME/Dancer2-2.2.0/changes
- http://www.openwall.com/lists/oss-security/2026/09/22/3