Skip to main content
Mallory
UnratedVulnerability

CVE-2026-28970: CRLF injection in SwiftNIO HTTP/1.1 start line validation

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-28970CWE-93

SwiftNIO contains a CRLF injection vulnerability in outbound HTTP/1.1 request and response start line components caused by insufficient validation in NIOHTTPRequestHeadersValidator and NIOHTTPResponseHeadersValidator. According to the provided advisory, validation was missing or inadequate for request URIs, custom HTTP methods, and response reason phrases, allowing attacker-controlled carriage return and line feed characters to be injected into HTTP/1.1 start lines. This can corrupt HTTP message framing and enable downstream protocol interpretation issues.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can enable HTTP request smuggling and HTTP response splitting. An attacker may be able to inject additional HTTP requests or responses onto the wire, which can lead to bypass of intermediary security controls such as WAFs, cache poisoning, and other downstream impacts depending on how affected proxies, caches, or back-end systems process the malformed traffic.

Mitigation

If you can’t patch tonight, do this now.

As a temporary workaround, ensure all user-controlled input is strictly sanitized before being used in HTTP start line components, specifically request URIs, custom HTTP methods, and response reason phrases. Reject or encode CR and LF characters and avoid passing unsanitized external input into outbound HTTP/1.1 request or response construction. This mitigation is temporary and may be error-prone compared with upgrading.

Remediation

Patch, then assume compromise.

Upgrade SwiftNIO to version 2.100.0 or later. The fixed version adds validation for request URIs, custom HTTP methods, and response reason phrases in the relevant validator handlers to prevent CRLF injection in outbound HTTP/1.1 start line components.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-28970 exploited in the wild?
As of Jun 13, 2026, Mallory has no reports of CVE-2026-28970 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-28970?
As of Jun 13, 2026, Mallory has found no public exploit for CVE-2026-28970.
Is there a patch for CVE-2026-28970?
Upgrade SwiftNIO to version 2.100.0 or later. The fixed version adds validation for request URIs, custom HTTP methods, and response reason phrases in the relevant validator handlers to prevent CRLF injection in outbound HTTP/1.1 start line components.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.