How severe is GHSA-7fj7-39wj-c64f?

GHSA-7fj7-39wj-c64f has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7fj7-39wj-c64f?

GHSA-7fj7-39wj-c64f affects the following packages: github.com/apple/swift-nio (SwiftURL), github.com/apple/swift-nio (SwiftURL), github.com/apple/swift-nio (SwiftURL). Ecosystems affected: SwiftURL.

How do I fix GHSA-7fj7-39wj-c64f?

Update github.com/apple/swift-nio to 2.42.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fj7-39wj-c64f is resolved across your whole dependency graph.

How do I detect GHSA-7fj7-39wj-c64f in my SwiftURL dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apple/swift-nio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7fj7-39wj-c64f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7fj7-39wj-c64f?

O3 pinpoints whether GHSA-7fj7-39wj-c64f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7fj7-39wj-c64f actively exploited in the wild?

No public exploit code has been indexed for GHSA-7fj7-39wj-c64f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7fj7-39wj-c64f?

GHSA-7fj7-39wj-c64f has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-7fj7-39wj-c64f?

GHSA-7fj7-39wj-c64f is classified as CWE-113 (CWE-113), CWE-74 (CWE-74). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7fj7-39wj-c64f published, and has it been updated?

GHSA-7fj7-39wj-c64f was published on June 7, 2023 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 SwiftURL

GHSA-7fj7-39wj-c64f

MEDIUM

SwiftNIO vulnerable to Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')

Also known asCVE-2022-3215

Published

Jun 7, 2023

Updated

Mar 13, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk41th percentile+0.29%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

📦github.com/apple/swift-nio📦github.com/apple/swift-nio📦github.com/apple/swift-nio

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects SwiftURL packages — download data is not available via public APIs for these ecosystems.

Description

NIOHTTP1 and projects using it for generating HTTP responses, including SwiftNIO, can be subject to a HTTP Response Injection attack. This occurs when a HTTP/1.1 server accepts user generated input from an incoming request and reflects it into a HTTP/1.1 response header in some form. A malicious user can add newlines to their input (usually in encoded form) and "inject" those newlines into the returned HTTP response.

This capability allows users to work around security headers and HTTP/1.1 framing headers by injecting entirely false responses or other new headers. The injected false responses may also be treated as the response to subsequent requests, which can lead to XSS, cache poisoning, and a number of other flaws.

This issue was resolved by adding a default channel handler that polices outbound headers. This channel handler is added by default to channel pipelines, but can be removed by users if they are doing this validation themselves.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦SwiftURL	`github.com/apple/swift-nio`	≥ 2.41.0&&< 2.42.0	2.42.0
📦SwiftURL	`github.com/apple/swift-nio`	≥ 2.39.0&&< 2.39.1	2.39.1
📦SwiftURL	`github.com/apple/swift-nio`	all versions	2.29.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/apple/swift-nio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/apple/swift-nio to 2.42.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7fj7-39wj-c64f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7fj7-39wj-c64f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7fj7-39wj-c64f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`NIOHTTP1` and projects using it for generating HTTP responses, including SwiftNIO, can be subject to a HTTP Response Injection attack. This occurs when a HTTP/1.1 server accepts user generated input from an incoming request and reflects it into a HTTP/1.1 response header in some form. A malicious user can add newlines to their input (usually in encoded form) and "inject" those newlines into the returned HTTP response. This capability allows users to work around security headers and HTTP/1.1 framing headers by injecting entirely false responses or other new headers. The injected false respons

O3 Security · Impact-Aware SCA

Is GHSA-7fj7-39wj-c64f in your dependencies?

O3 detects GHSA-7fj7-39wj-c64f across SwiftURL dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works