CVE-2026-28898: swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header values for control characters before placing them into the translated HTTP/1.1 message. in Apple swift-nio-http2
swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header values for control characters before placing them into the translated HTTP/1.1 message. swift-nio-http2 1.44.1 adds validation of all pseudo-header values (:path, :authority, :scheme, :method, and :status) at both the HPACK header validation layer and the HTTP/2-to-HTTP/1.1 translation layer. Requests or responses containing CR, LF, or NUL bytes in any pseudo-header value are now rejected with a connection error. This issue is fixed in swift-nio-http2 1.44.1.
AI Analysis
Technical Summary
Apple swift-nio-http2's HTTP/2-to-HTTP/1.1 codec failed to validate pseudo-header values for control characters (CR, LF, NUL) before placing them into the translated HTTP/1.1 message. This vulnerability could allow malformed pseudo-header values to be processed improperly. Version 1.44.1 of swift-nio-http2 addresses this by adding validation at both the HPACK header validation layer and the HTTP/2-to-HTTP/1.1 translation layer, rejecting requests or responses containing these control characters with a connection error.
Potential Impact
Improper validation of pseudo-header values could lead to malformed HTTP/1.1 messages, which may cause unexpected behavior in downstream HTTP processing or intermediaries. The exact impact is not detailed in the provided data, and no known exploits are reported. The fix prevents such malformed headers from being processed by rejecting them at the connection level.
Mitigation Recommendations
Upgrade to swift-nio-http2 version 1.44.1 or later, which includes validation of all pseudo-header values and rejects those containing control characters with a connection error. No other mitigation is indicated or required.
CVE-2026-28898: swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header values for control characters before placing them into the translated HTTP/1.1 message. in Apple swift-nio-http2
Description
swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header values for control characters before placing them into the translated HTTP/1.1 message. swift-nio-http2 1.44.1 adds validation of all pseudo-header values (:path, :authority, :scheme, :method, and :status) at both the HPACK header validation layer and the HTTP/2-to-HTTP/1.1 translation layer. Requests or responses containing CR, LF, or NUL bytes in any pseudo-header value are now rejected with a connection error. This issue is fixed in swift-nio-http2 1.44.1.
CVSS v3.1
Score 5.3medium
Affected software
pkg:swift/apple/swift-nio-http2Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apple swift-nio-http2's HTTP/2-to-HTTP/1.1 codec failed to validate pseudo-header values for control characters (CR, LF, NUL) before placing them into the translated HTTP/1.1 message. This vulnerability could allow malformed pseudo-header values to be processed improperly. Version 1.44.1 of swift-nio-http2 addresses this by adding validation at both the HPACK header validation layer and the HTTP/2-to-HTTP/1.1 translation layer, rejecting requests or responses containing these control characters with a connection error.
Potential Impact
Improper validation of pseudo-header values could lead to malformed HTTP/1.1 messages, which may cause unexpected behavior in downstream HTTP processing or intermediaries. The exact impact is not detailed in the provided data, and no known exploits are reported. The fix prevents such malformed headers from being processed by rejecting them at the connection level.
Mitigation Recommendations
Upgrade to swift-nio-http2 version 1.44.1 or later, which includes validation of all pseudo-header values and rejects those containing control characters with a connection error. No other mitigation is indicated or required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apple
- Date Reserved
- 2026-03-03T16:36:03.983Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3d7af74853345fc155f0e7
Added to database: 06/25/2026, 19:01:11 UTC
Last enriched: 06/25/2026, 19:16:00 UTC
Last updated: 06/25/2026, 20:12:36 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.