@fastify/cors is the CORS plugin for the Fastify web framework. In versions 8.2.0 through 11.3.x, an application that registers the plugin with the non-default onSend hook option crashes on a CORS preflight. On an OPTIONS request that carries the Origin and Access-Control-Request-Method headers, the plugin calls reply.send from inside the onSend hook and re-enters the send pipeline, so a second write of the response headers throws an uncaught ERR_HTTP_HEADERS_SENT that can terminate the Node.js process when no process-level handler is installed. An unauthenticated remote client can trigger this with a single preflight request, so the impact is availability only, and exploitation requires the non-default onSend configuration. The issue is fixed in @fastify/cors 11.4.0, where onSend is no longer an accepted hook value and registration fails with a clear error instead of crashing at request time, and users should upgrade to 11.4.0 or later. As a workaround, use any other hook such as the default onRequest, or set preflight to false.
History

Thu, 05 Nov 2026 00:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Low


Tue, 03 Nov 2026 17:00:00 +0000

Type Values Removed Values Added
First Time appeared Fastify
Fastify cors
Vendors & Products Fastify
Fastify cors

Mon, 02 Nov 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Mon, 02 Nov 2026 10:30:00 +0000

Type Values Removed Values Added
Description @fastify/cors is the CORS plugin for the Fastify web framework. In versions 8.2.0 through 11.3.x, an application that registers the plugin with the non-default onSend hook option crashes on a CORS preflight. On an OPTIONS request that carries the Origin and Access-Control-Request-Method headers, the plugin calls reply.send from inside the onSend hook and re-enters the send pipeline, so a second write of the response headers throws an uncaught ERR_HTTP_HEADERS_SENT that can terminate the Node.js process when no process-level handler is installed. An unauthenticated remote client can trigger this with a single preflight request, so the impact is availability only, and exploitation requires the non-default onSend configuration. The issue is fixed in @fastify/cors 11.4.0, where onSend is no longer an accepted hook value and registration fails with a clear error instead of crashing at request time, and users should upgrade to 11.4.0 or later. As a workaround, use any other hook such as the default onRequest, or set preflight to false.
Title @fastify/cors vulnerable to Denial of Service on a CORS preflight with the onSend hook
Weaknesses CWE-248
References
Metrics cvssV3_1

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


cve-icon MITRE

Status: PUBLISHED

Assigner: openjs

Published: 2026-11-02T10:20:47.667Z

Updated: 2026-11-02T17:04:11.417Z

Reserved: 2026-10-31T15:01:18.624Z

Link: CVE-2026-120215

cve-icon Vulnrichment

Updated: 2026-11-02T17:04:03.074Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-02T11:17:31.413

Modified: 2026-11-02T17:17:39.737

Link: CVE-2026-120215

cve-icon Redhat

Severity : Low

Publid Date: 2026-11-02T10:20:47Z

Links: CVE-2026-120215 - Bugzilla