Quick answers
- Is CVE-2026-64785 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64785 being exploited in the wild.
- How severe is CVE-2026-64785?
- Medium severity, with a CVSS score of 5.3, published 23 July 2026.
- Which products and versions are affected?
- swift-nio-http2 (Swift) < 1.45.0.
- Is there a fix for CVE-2026-64785?
- A patch was published on 1.45.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64785 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-64785?
- Check whether you run Apple SwiftNIO HTTP2 or swift-nio-http2 (Swift) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
SwiftNIO HTTP/2 fails to properly validate inbound HEADERS frames for control characters like CR, LF, NUL, and SP when using the HTTP2ToHTTP1Codec. Regular header values were only checked against a forbidden-name list, allowing attackers to inject CRLF sequences to terminate fields early and inject extra headers into outbound HTTP/1.1 messages. Additionally, pseudo-headers like ':path' were not checked for spaces, allowing for request-target manipulation that causes parser differentials in downstream HTTP/1.1 backends. This vulnerability is primarily reachable in pipelines that skip outbound validation or trust pre-validated headers. The issue is fixed in version 1.45.0.
Affected products
- Apple swift-nio-http2 < 1.45.0
Identifiers
- CVE-2026-64785
- GHSA-q3g2-m552-3r9c
Timeline
- 2026-07-23: disclosed
- 2026-07-24: advisory
- 1.45.0: patched