CVE-2026-28980: SwiftNIO NIOHTTP1 Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-rj37-6j9x-74q6
CWE-400 CWE-770
Published
Advisory Summary

CVE-2026-28980 is a HIGH denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting SwiftNIO NIOHTTP1 libraries in the SwiftURL ecosystem. The issue involves httpdecoder accepts unbounded http/1 header blocks, enabling remote dos. Remediation is available by upgrading affected packages to version 2.100.0.

CVE-2026-28980 at a Glance

CVE Identifier CVE-2026-28980
GHSA Identifier GHSA-rj37-6j9x-74q6
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product SwiftNIO NIOHTTP1
Package Ecosystem SwiftURL
Published Date
Last Updated

How to Fix CVE-2026-28980

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

github.com/apple/swift-nio fixed: 2.100.0
Upgrade github.com/apple/swift-nio to 2.100.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 github.com/apple/swift-nio

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-28980, inspect your project dependencies for SwiftNIO NIOHTTP1:

inspect dependencies for github.com/apple/swift-nio

Analyze the terminal output to locate any version of SwiftNIO NIOHTTP1 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.100.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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In SwiftNIO NIOHTTP1, 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 The `HTTPDecoder` in `NIOHTTP1` enforces no limit on the total size of an HTTP/1 message's header block or on the number of header fields per message. A remote peer can submit an arbitrary number of small, valid headers in a single request and have them all accumulated into the resulting `HTTPHeaders` value before any application code runs. This can be used to exhaust memory, or — for consumers that subsequently convert headers into `swift-http-types`' `HTTPFields` — to crash the process. ### Details `HTTPDecoder` previously enforced only a single hardcoded parsing limit: 80 KB per individual header field (name + value). There was no cap on the cumulative size of the header block, nor on the number of header fields per message. Because each individual field can remain well below the 80 KB threshold, a peer can submit hundreds of thousands of valid headers in a single request, all of which are appended to the decoded `HTTPHeaders` without bound. The headers are then visible to user code through the standard `HTTPServerRequestPart.head` / `HTTPClientResponsePart.head` events. Two observed downstream effects: - **Hummingbird 2** (and other consumers that bridge `HTTPHeaders` into `swift-http-types`' `HTTPFields`) crashes via a precondition failure inside `HTTPFields` once the configured field count is exceeded. - **Vapor 4** does not crash, but the per-request memory footprint scales linearly with the number of headers received, allowing a single connection to inflate server memory use substantially. ### Impact A single unauthenticated remote peer can trigger a denial of service against any HTTP/1 server (or, in the response direction, any HTTP/1 client) built on `NIOHTTP1` — either by crashing the process, depending on the downstream framework, or by driving the process's resident memory to arbitrary sizes. ### Patches This issue is addressed in `swift-nio` 2.100.0 and later. The `HTTPDecoder` now applies three parsing limits with conservative defaults, exposed through the new `NIOHTTPDecoderLimitConfiguration` type: | Limit | Default | | --- | --- | | `maxHeaderFieldSize` | 80 KB | | `maxHeaderListSize` | 2 MB | | `maxHeaderFieldCount` | 256 | Exceeding any of these limits causes the decoder to fail with `HTTPParserError.headerOverflow`. The configuration can be supplied directly to `HTTPRequestDecoder` / `HTTPResponseDecoder`, or via the `decoderConfiguration` property on `NIOUpgradableHTTPServerPipelineConfiguration` and `NIOUpgradableHTTPClientPipelineConfiguration`. Users who require larger limits — for example, applications that legitimately exchange very large header blocks — can opt into them explicitly by constructing a custom `NIOHTTPDecoderLimitConfiguration`. ### Workarounds Users unable to upgrade can mitigate by placing a reverse proxy in front of the service that enforces equivalent limits on request header count and total header size. ### Credit This issue was reported by @Joannis. SwiftNIO thanks @Joannis for the report and the support in landing the fix.

CVE-2026-28980 Affected SwiftNIO NIOHTTP1 Versions

1 component(s)
Fixed Versions:
2.100.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/apple/swift-nio
SwiftURL
< 2.100.0
2.100.0

References

Frequently Asked Questions

What is CVE-2026-28980?
CVE-2026-28980 is a security vulnerability in SwiftNIO NIOHTTP1 involving HTTPDecoder accepts unbounded HTTP/1 header blocks, enabling remote DoS under CWE-400: Uncontrolled Resource Consumption.
Which SwiftNIO NIOHTTP1 versions are affected?
Affected versions include releases prior to 2.100.0 across affected packages: github.com/apple/swift-nio.
What version fixes CVE-2026-28980?
Upgrading to 2.100.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/apple/swift-nio affected?
Yes, github.com/apple/swift-nio is affected in releases prior to 2.100.0. Upgrade your dependency to 2.100.0 or later.
What CWE is associated with CVE-2026-28980?
CVE-2026-28980 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check SwiftURL dependencies for CVE-2026-28980?
Run the dependency tree command: 'inspect dependencies for github.com/apple/swift-nio'. 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-rj37-6j9x-74q6",
  "modified" : "2026-06-12T15:07:53Z",
  "published" : "2026-06-12T15:07:53Z",
  "aliases" : [ "CVE-2026-28980" ],
  "summary" : "SwiftNIO NIOHTTP1:  HTTPDecoder accepts unbounded HTTP/1 header blocks, enabling remote DoS",
  "details" : "### Summary\n\nThe `HTTPDecoder` in `NIOHTTP1` enforces no limit on the total size of an HTTP/1 message's header block or on the number of header fields per message. A remote peer can submit an arbitrary number of small, valid headers in a single request and have them all accumulated into the resulting `HTTPHeaders` value before any application code runs. This can be used to exhaust memory, or — for consumers that subsequently convert headers into `swift-http-types`' `HTTPFields` — to crash the process.\n\n### Details\n\n`HTTPDecoder` previously enforced only a single hardcoded parsing limit: 80 KB per individual header field (name + value). There was no cap on the cumulative size of the header block, nor on the number of header fields per message. Because each individual field can remain well below the 80 KB threshold, a peer can submit hundreds of thousands of valid headers in a single request, all of which are appended to the decoded `HTTPHeaders` without bound.\n\nThe headers are then visible to user code through the standard `HTTPServerRequestPart.head` / `HTTPClientResponsePart.head` events. Two observed downstream effects:\n\n  - **Hummingbird 2** (and other consumers that bridge `HTTPHeaders` into `swift-http-types`' `HTTPFields`) crashes via a precondition failure inside `HTTPFields` once the configured field count is exceeded.\n  - **Vapor 4** does not crash, but the per-request memory footprint scales linearly with the number of headers received, allowing a single connection to inflate server memory use substantially.\n  \n### Impact\n\nA single unauthenticated remote peer can trigger a denial of service against any HTTP/1 server (or, in the response direction, any HTTP/1 client) built on `NIOHTTP1` — either by crashing the process, depending on the downstream framework, or by driving the process's resident memory to arbitrary sizes.\n\n### Patches\n\nThis issue is addressed in `swift-nio` 2.100.0 and later.\n\nThe `HTTPDecoder` now applies three parsing limits with conservative defaults, exposed through the new `NIOHTTPDecoderLimitConfiguration` type:\n\n  | Limit | Default |\n  | --- | --- |\n  | `maxHeaderFieldSize` | 80 KB |\n  | `maxHeaderListSize` | 2 MB |\n  | `maxHeaderFieldCount` | 256 |\n\nExceeding any of these limits causes the decoder to fail with `HTTPParserError.headerOverflow`. The configuration can be supplied directly to `HTTPRequestDecoder` / `HTTPResponseDecoder`, or via the `decoderConfiguration` property on `NIOUpgradableHTTPServerPipelineConfiguration` and `NIOUpgradableHTTPClientPipelineConfiguration`.\n\nUsers who require larger limits — for example, applications that legitimately exchange very large header blocks — can opt into them explicitly by constructing a custom `NIOHTTPDecoderLimitConfiguration`.\n\n### Workarounds\n\nUsers unable to upgrade can mitigate by placing a reverse proxy in front of the service that enforces equivalent limits on request header count and total header size.\n\n### Credit\n\nThis issue was reported by @Joannis. SwiftNIO thanks @Joannis for the report and the support in landing the fix.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "SwiftURL",
      "name" : "github.com/apple/swift-nio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.100.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.99.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apple/swift-nio/security/advisories/GHSA-rj37-6j9x-74q6"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apple/swift-nio"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400", "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-12T15:07:53Z",
    "nvd_published_at" : null
  }
}