{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-120216","id":"CVE-2026-120216","title":"Fastify denial of service in streaming response timeouts","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 un","descriptionLong":"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.","published":"2026-11-02T11:08:00.038Z","updated":"2026-11-09T10:45:34.317385692Z","reserved":"2026-10-31T16:06:34.967Z","status":"Awaiting Analysis","rejected":false,"assigner":"openjs","metric":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"openjs"},"metrics":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"openjs"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"ce714d77-add3-4f53-aff5-83d477b104bb"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"OSV"}],"rating":"medium","products":["fastify"],"affectedProducts":[{"vendor":"fastify","product":"fastify","defaultStatus":"unaffected","versions":[{"versionType":"semver","status":"affected","version":"5.8.0","lessThan":"5.12.8"},{"versionType":"semver","status":"unaffected","version":"5.12.8"}],"platforms":[]}],"packages":[],"cwes":["CWE-248"],"aliases":["GHSA-3qgw-9275-xf8w"],"references":[{"url":"https://github.com/fastify/fastify/security/advisories/GHSA-3qgw-9275-xf8w","tags":["advisory"]},{"url":"https://cna.openjsf.org/security-advisories.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/120xxx/CVE-2026-120216.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-120216","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00329,"epssPercentile":0.26529,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-120216","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-120216","ok":true,"note":"Awaiting Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-120216","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-120216","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}