CVE-2026-93711

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-22. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (3)

Auto-updated Sep 22, 2026
No patch confirmed yet.
generic

Client Challenge

https://metacpan.org/release/CROMEDOME/Dancer2-2.2.0/changes
generic
https://github.com/PerlDancer/Dancer2/commit/ff89ac12af7b8899812a79e9924dfea7a5d9833b.patch
generic

CR and LF were not stripped from response header names · Issue #1822 · PerlDancer/Dancer2 · GitHub

https://github.com/PerlDancer/Dancer2/issues/1822

Vendor Advisories for CVE-2026-93711(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 03:47 UTCEG score recompute
  2. 2026-10-04 03:47 UTCGHSA enrichment
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 05:14 UTCEG score recompute
  5. 2026-10-03 05:14 UTCGHSA enrichment
  6. 2026-10-02 06:40 UTCEG score recompute
  7. 2026-10-02 06:40 UTCGHSA enrichment
  8. 2026-10-01 19:51 UTCEPSS rescore
  9. 2026-10-01 08:04 UTCEG score recompute
  10. 2026-10-01 08:04 UTCGHSA enrichment
  11. 2026-09-30 15:04 UTCEPSS rescore
  12. 2026-09-30 09:31 UTCEG score recompute
  13. 2026-09-30 09:31 UTCGHSA enrichment
  14. 2026-09-29 10:49 UTCEG score recompute
  15. 2026-09-29 10:49 UTCGHSA enrichment
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 12:16 UTCEG score recompute
  19. 2026-09-28 12:16 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 13:43 UTCEG score recompute
  22. 2026-09-27 13:43 UTCGHSA enrichment
  23. 2026-09-26 15:59 UTCEPSS rescore
  24. 2026-09-26 15:05 UTCEG score recompute
  25. 2026-09-26 15:05 UTCGHSA enrichment
Show 19 more
  1. 2026-09-25 16:32 UTCGHSA enrichment
  2. 2026-09-24 17:59 UTCEG score recompute
  3. 2026-09-24 17:59 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-23 19:07 UTCEG score recompute
  6. 2026-09-23 19:07 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-22 20:32 UTCGHSA enrichment
  9. 2026-09-22 19:33 UTCEG score recompute▲ 6.50
  10. 2026-09-22 19:33 UTCGHSA enrichment
  11. 2026-09-22 19:32 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  12. 2026-09-22 19:13 UTCEG score recompute
  13. 2026-09-22 19:13 UTCGHSA enrichment
  14. 2026-09-22 16:01 UTCEPSS rescore
  15. 2026-09-22 03:30 UTCNVD update
  16. 2026-09-22 02:25 UTCMITRE cvelistV5
  17. 2026-09-22 01:28 UTCNVD update
  18. 2026-09-22 00:56 UTCEG score recompute
  19. 2026-09-22 00:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-93711?
CVE-2026-93711 is a medium vulnerability published on September 22, 2026. Dancer2 versions before 2.2.0 for Perl do not strip CR and LF from response header names in headerstoarray. 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…
When was CVE-2026-93711 disclosed?
CVE-2026-93711 was first published on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93711 actively exploited?
CVE-2026-93711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93711?
CVE-2026-93711 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-93711?
No fix for CVE-2026-93711 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93711 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93711

Explore →

Is Your Infrastructure Affected by CVE-2026-93711?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs