CVE-2026-64785

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

SwiftNIO HTTP/2 was missing validation on inbound HEADERS frames that let CR, LF, NUL, SP and other control characters reach an HTTP/1.1 backend through NIOHTTP2's HTTP/2-to-HTTP/1 codec, enabling HTTP request smuggling or response splitting. This vulnerability is addressed in swift-nio-http2 version 1.45.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 23, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Jul 26, 2026
Patch available. Sources: github.
github Patch Available

Missing CR/LF/NUL validation in header values · Advisory · apple/swift-nio-http2 · GitHub

https://github.com/apple/swift-nio-http2/security/advisories/GHSA-q3g2-m552-3r9c

Vendor Advisories for CVE-2026-64785(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 7× in last 7d / 42× 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-14 16:13 UTCEG score recompute
  2. 2026-09-12 16:00 UTCEG score recompute
  3. 2026-09-11 16:42 UTCEG score recompute
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 15:06 UTCEG score recompute
  7. 2026-09-09 08:54 UTCEG score recompute
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 21:29 UTCEG score recompute
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 18:46 UTCEG score recompute
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 19:27 UTCEG score recompute
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 13:14 UTCEG score recompute
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 13:11 UTCEG score recompute
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-30 23:47 UTCEG score recompute
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-30 00:30 UTCEG score recompute
  25. 2026-08-28 21:42 UTCEPSS rescore
Show 63 more
  1. 2026-08-28 03:38 UTCEG score recompute
  2. 2026-08-27 04:19 UTCEG score recompute
  3. 2026-08-26 14:47 UTCEPSS rescore
  4. 2026-08-26 04:53 UTCEG score recompute
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-25 05:34 UTCEG score recompute
  7. 2026-08-23 06:58 UTCEG score recompute
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 07:40 UTCEG score recompute
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 09:04 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 09:46 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 10:28 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 11:10 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 11:52 UTCEG score recompute
  20. 2026-08-15 12:35 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 13:17 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 14:34 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-11 15:17 UTCEG score recompute
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-09 16:36 UTCEG score recompute
  29. 2026-08-09 13:47 UTCEPSS rescore
  30. 2026-08-07 18:01 UTCEG score recompute
  31. 2026-08-06 18:43 UTCEG score recompute
  32. 2026-08-06 13:47 UTCEPSS rescore
  33. 2026-08-05 19:25 UTCEG score recompute
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 20:08 UTCEG score recompute
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 10:39 UTCEPSS rescore
  39. 2026-08-03 20:50 UTCEG score recompute
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 21:33 UTCEG score recompute
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-07-30 23:37 UTCEG score recompute
  44. 2026-07-30 16:28 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-29 01:01 UTCEG score recompute
  48. 2026-07-28 15:37 UTCEPSS rescore
  49. 2026-07-28 01:43 UTCEG score recompute
  50. 2026-07-27 14:14 UTCEPSS rescore
  51. 2026-07-27 02:25 UTCEG score recompute
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 03:07 UTCEG score recompute
  55. 2026-07-25 14:18 UTCEPSS rescore
  56. 2026-07-25 14:18 UTCEPSS rescore
  57. 2026-07-24 20:42 UTCEG score recompute▲ 5.30
  58. 2026-07-24 20:41 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  59. 2026-07-24 14:18 UTCEPSS rescore
  60. 2026-07-24 14:18 UTCEPSS rescore
  61. 2026-07-23 20:22 UTCNVD update
  62. 2026-07-23 19:22 UTCEG score recompute
  63. 2026-07-23 19:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64785?
CVE-2026-64785 is a medium vulnerability published on July 23, 2026. SwiftNIO HTTP/2 was missing validation on inbound HEADERS frames that let CR, LF, NUL, SP and other control characters reach an HTTP/1.1 backend through NIOHTTP2's HTTP/2-to-HTTP/1 codec, enabling HTTP request smuggling or response splitting. This vulnerability is addressed in swift-nio-http2…
When was CVE-2026-64785 disclosed?
CVE-2026-64785 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64785 actively exploited?
CVE-2026-64785 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 92.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64785?
CVE-2026-64785 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-64785?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64785, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64785?

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

Start Free Scan →Browse All CVEs