CVE-2026-92081

fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses

Published Sep 16, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
fastify is a fast and low-overhead web framework for Node.js. In versions before 5.12.5, when a route registers a response trailer via reply.trailer() and is served over HTTP/2, fastify unconditionally sets the Transfer-Encoding: chunked header, which is forbidden on HTTP/2, so Node.js throws while serializing the response headers. The exception is not caught and becomes an uncaughtException, so a single unauthenticated HTTP/2 request to any route that uses trailers crashes the server process and drops all in-flight requests, and it can be repeated on every restart. The issue is fixed in fastify 5.12.5, and users should upgrade to 5.12.5 or later. As a workaround, avoid registering response trailers with reply.trailer() on routes served over HTTP/2 until upgrading.

Analysis

AI-generated

Technical impact

A bug in fastify versions before 5.12.5 causes a node process to crash when a route registers a response trailer with reply.trailer() and the request is served over HTTP/2. The mishandled header results in Node.js throwing an uncaught exception that terminates the server process. A single unauthenticated HTTP/2 request to any affected route triggers the crash and aborts all in‑flight requests, effectively denying service until the process restarts.

Affected Systems

The affected product is the fastify web framework for Node.js. All releases prior to 5.12.5 are vulnerable. The fix is included in fastify 5.12.5 and later.

Risk and Exploitability

The vulnerability has a CVSS score of 5.9, indicating moderate severity, and the EPSS score is < 1%; it is not listed in the CISA KEV catalog. The attack vector is remote and unauthenticated: any client able to send an HTTP/2 request can trigger the crash. Because no authentication or privileged state is required, the exploit likelihood is high in environments that enable HTTP/2 and use the trailer feature.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade fastify to version 5.12.5 or later
  • Refactor or remove reply.trailer() usage on HTTP/2 routes until the upgrade is applied
  • Restart the server after applying the patch to ensure changes take effect

Generated by OpenCVE AI on September 18, 2026 at 12:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4mh8-r7rc-xpvc fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses
History
Type Values Removed Values Added
First Time appeared Fastify
Fastify fastify
Vendors & Products Fastify
Fastify fastify
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description fastify is a fast and low-overhead web framework for Node.js. In versions before 5.12.5, when a route registers a response trailer via reply.trailer() and is served over HTTP/2, fastify unconditionally sets the Transfer-Encoding: chunked header, which is forbidden on HTTP/2, so Node.js throws while serializing the response headers. The exception is not caught and becomes an uncaughtException, so a single unauthenticated HTTP/2 request to any route that uses trailers crashes the server process and drops all in-flight requests, and it can be repeated on every restart. The issue is fixed in fastify 5.12.5, and users should upgrade to 5.12.5 or later. As a workaround, avoid registering response trailers with reply.trailer() on routes served over HTTP/2 until upgrading.
Title fastify vulnerable to Denial of Service via unhandled exception on HTTP/2 trailer responses
Weaknesses CWE-248
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
openjs
Published
Updated
Sep 16, 2026, 2:00 PM
Reserved
Sep 15, 2026, 12:55 PM
Status
Awaiting Analysis
Published
Sep 16, 2026, 9:17 AM
Modified
Sep 16, 2026, 7:40 PM
Severity
Moderate
Public date
Sep 16, 2026, 8:52 AM