cve.bz

CVE-2026-28898 apple swiftnio http\/2: Improper Encoding or Escaping of Output

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in apple swiftnio http\/2. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/apple/swift-nio-http2 1.44.0.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-06-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • github.com/apple/swift-nio-http2 (SwiftURL): fixed in 1.44.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-28898 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-28898?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-28898?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-28898 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-28898

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-28898](https://cve.bz/cve/badge/CVE-2026-28898.svg)](https://cve.bz/cve/CVE-2026-28898)

HTML:

<a href="https://cve.bz/cve/CVE-2026-28898"><img src="https://cve.bz/cve/badge/CVE-2026-28898.svg" alt="CVE-2026-28898"></a>

Affected

  • apple:swiftnio_http\/2

Versions

From the CNA's record in the CVE List.

ProductAffected
Apple swift-nio-http2before 1.44.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4px2-pw77-vc85SwiftURLgithub.com/apple/swift-nio-http2<1.44.01.44.0

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON