CVE-2026-64785: swift-nio-http2 Missing CR/LF/NUL Validation Vulnerability

MODERATE
Advisory Identifier: GHSA-q3g2-m552-3r9c
CVSS 5.3
CWE-113 CWE-444
Published
Advisory Summary

CVE-2026-64785 is a MODERATE (CVSS 5.3) missing cr/lf/nul validation vulnerability (CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')) affecting swift-nio-http2 libraries in the SwiftURL ecosystem. The issue involves missing cr/lf/nul validation in header values. Remediation is available by upgrading affected packages to version 1.45.0.

CVE-2026-64785 at a Glance

CVE Identifier CVE-2026-64785
GHSA Identifier GHSA-q3g2-m552-3r9c
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Affected Product swift-nio-http2
Package Ecosystem SwiftURL
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-64785

To remediate this vulnerability, upgrade all affected swift-nio-http2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

swift-nio-http2 fixed: 1.45.0
Upgrade swift-nio-http2 to 1.45.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for swift-nio-http2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-64785, inspect your project dependencies for swift-nio-http2:

inspect dependencies for swift-nio-http2

Analyze the terminal output to locate any version of swift-nio-http2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.45.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'), where the product receives data from an http agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes cr and lf characters before the data is included in outgoing http headers. In swift-nio-http2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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. ## Impact Two related gaps in inbound header validation, against any application using HTTP2ToHTTP1Codec (or HTTP2FramePayloadToHTTP1Codec) to front an HTTP/1.1 backend: Regular header field values were only checked against a forbidden-name list (connection, transfer-encoding, proxy-connection, keep-alive, upgrade); the value itself was never inspected. An attacker-controlled regular header field value containing CR or LF passed validation and, once serialized as `name: value CRLF` by the codec, terminated the field early and injected extra header lines into the outbound HTTP/1.1 message. Pseudo-header values (`:path` in particular) were only checked against CR, LF and NUL. A `:path` value containing SP serializes into the request-target of `METHOD SP request-target SP HTTP-version CRLF`, so a value like `/a HTTP/1.1` produces `GET /a HTTP/1.1 HTTP/1.1` — a parser-differential request line depending on whether a downstream reader takes the first or last SP-delimited token as the version. Neither of these is reachable on a stock pipeline: NIOHTTP1's outbound validator (`enableOutboundHeaderValidation`, on by default) already rejects these characters on write. The exposure is pipelines that skip outbound validation, or any code that reads validated-looking `HTTPRequestHead.headers` and forwards the values on trusting that HTTP/2 already checked them. ## Fix Fixed in 48bfd90 and 45bdf67. ## Mitigation Upgrade to 1.45.0

CVE-2026-64785 Affected swift-nio-http2 Versions

1 component(s)
Fixed Versions:
1.45.0
Product / Package Ecosystem Affected Versions Fixed Version
swift-nio-http2
SwiftURL
< 1.45.0
1.45.0

References

Frequently Asked Questions

What is CVE-2026-64785?
CVE-2026-64785 is a security vulnerability in swift-nio-http2 involving Missing CR/LF/NUL validation in header values under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting').
Which swift-nio-http2 versions are affected?
Affected versions include releases prior to 1.45.0 across affected packages: swift-nio-http2.
What version fixes CVE-2026-64785?
Upgrading to 1.45.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is swift-nio-http2 affected?
Yes, swift-nio-http2 is affected in releases prior to 1.45.0. Upgrade your dependency to 1.45.0 or later.
What is the CVSS score of CVE-2026-64785?
CVE-2026-64785 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-64785?
CVE-2026-64785 is classified under CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') (The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.).
How can I check SwiftURL dependencies for CVE-2026-64785?
Run the dependency tree command: 'inspect dependencies for swift-nio-http2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q3g2-m552-3r9c",
  "modified" : "2026-07-24T21:52:10Z",
  "published" : "2026-07-24T21:52:10Z",
  "aliases" : [ "CVE-2026-64785" ],
  "summary" : "swift-nio-http2: Missing CR/LF/NUL validation in header values",
  "details" : "## Summary\n\nSwiftNIO HTTP/2 was missing validation on inbound HEADERS frames that let\nCR, LF, NUL, SP and other control characters reach an HTTP/1.1 backend\nthrough NIOHTTP2's HTTP/2-to-HTTP/1 codec, enabling HTTP request smuggling\nor response splitting.\n\n## Impact\n\nTwo related gaps in inbound header validation, against any application\nusing HTTP2ToHTTP1Codec (or HTTP2FramePayloadToHTTP1Codec) to front an\nHTTP/1.1 backend:\n\nRegular header field values were only checked against a forbidden-name\nlist (connection, transfer-encoding, proxy-connection, keep-alive,\nupgrade); the value itself was never inspected. An attacker-controlled\nregular header field value containing CR or LF passed validation and, once\nserialized as `name: value CRLF` by the codec, terminated the field early\nand injected extra header lines into the outbound HTTP/1.1 message.\n\nPseudo-header values (`:path` in particular) were only checked against\nCR, LF and NUL. A `:path` value containing SP serializes into the\nrequest-target of `METHOD SP request-target SP HTTP-version CRLF`, so a\nvalue like `/a HTTP/1.1` produces `GET /a HTTP/1.1 HTTP/1.1` — a\nparser-differential request line depending on whether a downstream reader\ntakes the first or last SP-delimited token as the version.\n\nNeither of these is reachable on a stock pipeline: NIOHTTP1's outbound\nvalidator (`enableOutboundHeaderValidation`, on by default) already rejects\nthese characters on write. The exposure is pipelines that skip outbound\nvalidation, or any code that reads validated-looking `HTTPRequestHead.headers`\nand forwards the values on trusting that HTTP/2 already checked them.\n\n## Fix\n\nFixed in 48bfd90 and 45bdf67.\n\n## Mitigation\n\nUpgrade to 1.45.0",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "SwiftURL",
      "name" : "swift-nio-http2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.45.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apple/swift-nio-http2/security/advisories/GHSA-q3g2-m552-3r9c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64785"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apple/swift-nio-http2/commit/45bdf670248be5f16ec0340e125dca285536f0fb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apple/swift-nio-http2/commit/48bfd9067d7d1d15c4789440127a0cf36222ea43"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apple/swift-nio-http2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apple/swift-nio-http2/releases/tag/1.45.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-113", "CWE-444" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T21:52:10Z",
    "nvd_published_at" : "2026-07-23T20:17:21Z"
  }
}