CVE-2024-58384

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 5.4; sources differ by 0.0.

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

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

Tornado before 6.4.1 contains a CRLF injection vulnerability in CurlAsyncHTTPClient that fails to reject carriage return and line feed characters in request headers. Attackers can inject CRLF sequences into header values to inject arbitrary headers or construct entirely new HTTP requests.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Tornado before 6.4.1 CRLF Injection via CurlAsyncHTTPClient | Advisories | VulnCheck

https://www.vulncheck.com/advisories/tornado-before-6.4.1-crlf-injection-via-curlasynchttpclient
github Patch Available🟡 PoC Available

CRLF injection in CurlAsyncHTTPClient headers · Advisory · tornadoweb/tornado · GitHub

https://github.com/tornadoweb/tornado/security/advisories/GHSA-w235-7p84-xx57

Vendor Advisories for CVE-2024-58384(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
tornado0.2 ... 6.4b1 (72 versions)6.4.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 16× 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-09-18 22:13 UTCEG score recompute
  2. 2026-09-18 22:13 UTCGHSA enrichment
  3. 2026-09-18 19:26 UTCEPSS rescore
  4. 2026-09-17 20:18 UTCEG score recompute
  5. 2026-09-17 20:18 UTCGHSA enrichment
  6. 2026-09-17 19:39 UTCEG score recompute
  7. 2026-09-17 19:39 UTCGHSA enrichment
  8. 2026-09-17 15:40 UTCEG score recompute
  9. 2026-09-17 15:40 UTCGHSA enrichment
  10. 2026-09-16 14:06 UTCEPSS rescore
  11. 2026-09-16 14:06 UTCEPSS rescore
  12. 2026-09-16 13:44 UTCEG score recompute
  13. 2026-09-16 13:44 UTCGHSA enrichment
  14. 2026-09-15 16:33 UTCEG score recompute
  15. 2026-09-15 15:24 UTCEG score recompute
  16. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2024-58384?
CVE-2024-58384 is a medium vulnerability published on September 15, 2026. Tornado before 6.4.1 contains a CRLF injection vulnerability in CurlAsyncHTTPClient that fails to reject carriage return and line feed characters in request headers. Attackers can inject CRLF sequences into header values to inject arbitrary headers or construct entirely new HTTP requests.
When was CVE-2024-58384 disclosed?
CVE-2024-58384 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-58384 actively exploited?
CVE-2024-58384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.3% of all scored CVEs.
What is the CVSS score of CVE-2024-58384?
CVE-2024-58384 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2024-58384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58384, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58384

Explore →

Is Your Infrastructure Affected by CVE-2024-58384?

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

Start Free Scan →Browse All CVEs