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.
CVE-2026-64785
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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity53% × 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
July 24, 2026
Advisory Details (1)
Auto-updated Jul 26, 2026Missing 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-3r9cVendor 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 14× in last 7d / 14× 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.
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 02:25 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 20:42 UTCEG score recompute▲ 5.30
- 2026-07-24 20:41 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 20:22 UTCNVD update
- 2026-07-23 19:22 UTCEG score recompute
- 2026-07-23 19:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-444
Frequently asked(5)
What is CVE-2026-64785?
When was CVE-2026-64785 disclosed?
Is CVE-2026-64785 actively exploited?
What is the CVSS score of CVE-2026-64785?
How do I remediate CVE-2026-64785?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64785
Is Your Infrastructure Affected by CVE-2026-64785?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.