Public vulnerability disclosure

CVE-2026-120216

fastify vulnerable to Denial of Service via uncaught exception on handlerTimeout with streaming responses

publishedCWE-248

fastify is a web framework for Node.js. In versions 5.8.0 through 5.12.7, when the server is configured with a nonzero handlerTimeout and a route returns a streaming response, a request whose stream has already sent its headers but stays open past the timeout crashes the server. When the timeout fires, Fastify tries to send a new error response on a response that has already started, raising an uncaught ERR_HTTP_HEADERS_SENT that terminates the Node.js process and interrupts any other in-flight requests. An unauthenticated remote client can trigger this with a single request to an affected streaming endpoint, so the impact is availability only, and exploitation requires the non-default handlerTimeout to be set. The default handlerTimeout of 0 is not affected. The issue is fixed in fastify 5.12.8, and users should upgrade to 5.12.8 or later. As a workaround, set handlerTimeout to 0, which disables the affected timeout path.

Technical severity5.9 mediumCVSS 3.1 · CNA: openjs
Published2026-11-02Source updated 2026-11-02
Collected2026-11-022 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
fastify
fastify
fastify
npm
≥ 5.8.0; < 5.12.8 (affected, semver)
5.12.8 (unaffected, semver)
Other versions: unaffected
CNA: openjs

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 5.9
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCNA: openjs
3.1 / 5.9
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HNVD: ce714d77-add3-4f53-aff5-83d477b104bb

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References