CVE-2026-33011: Nest Fastify HEAD Request Middleware Bypass
Impact In a NestJS application using @nestjs/platform-fastify, GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist). As a result: - Middleware will be completely skipped. - The HTTP response won't include a body (since the response is truncated when redirecting a HEAD request to a GET handler).
Published Mar 17, 2026 · Updated Mar 20, 2026
Affected packages
@nestjs/platform-fastify
- Ecosystem
- npm
- Affected
- <= 11.1.15
- Fixed in
- 11.1.16
- Check
npm ls @nestjs/platform-fastify
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In a NestJS application using @nestjs/platform-fastify, GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist).
As a result:
- Middleware will be completely skipped.
- The HTTP response won't include a body (since the response is truncated when redirecting a HEAD request to a GET handler).
- The actual handler will still be executed.
Patches
Fixed in @nestjs/[email protected]
Credited to kamilmysliwiec.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesGHSA-9c5c-9qcx-q35q
@nestjs/platform-fastify: Path-scoped middleware bypass via absolute-form request targets
high7.4Sep 30, 2026CVE-2026-54281
Nest: Middleware Bypass on Fastify via Trailing Slash
high8.7Jun 15, 2026CVE-2026-2293
Nest has a Fastify URL Encoding Middleware Bypass
high8.2Mar 2, 2026CVE-2025-69211
Nest has a Fastify URL Encoding Middleware Bypass (TOCTOU)
medium6.9Dec 30, 2025
