# CVE-2026-120216: fastify vulnerable to Denial of Service via uncaught exception on handlerTimeout with streaming responses


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** CLSA-2026-1793801979, GHSA-3qgw-9275-xf8w

## What is CVE-2026-120216?

CVE-2026-120216 is a medium-severity vulnerability in fastify, published on 2 Nov 2026. 

### Official description

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.

Weakness: CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2026-120216?


## How do I fix CVE-2026-120216?

Upgrade to a fixed version.

## Is CVE-2026-120216 being exploited?

There is no known exploitation of CVE-2026-120216 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120216 and fix it if it is affected.

What it is: CVE-2026-120216 is a medium-severity vulnerability in fastify, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120216 in the wild and no public exploit code.

Affected product: fastify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120216/ (Markdown: https://insights.sbomify.com/CVE-2026-120216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120216
- OSV: https://osv.dev/vulnerability/CVE-2026-120216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120216/
Summaries are generated and may contain mistakes; the official description above is the record.
