Cyber Resilience

CVE-2026-33011

Nestjs Nest ≤ 11.1.16

Published
20 March 2026
Modified
23 March 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0035 27th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-33011 is a high-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Nestjs Nest. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-33011 affects the Nest framework, a platform for building scalable Node.js server-side applications, specifically in versions 11.1.15 and prior when using the @nestjs/platform-fastify adapter. The vulnerability arises because Fastify automatically redirects HEAD requests to corresponding GET handlers if they exist. This redirection causes GET middleware to be entirely skipped, results in an HTTP response without a body due to truncation during the HEAD-to-GET redirect, and still executes the underlying handler. The issue has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) and is associated with CWE-670 (Always-Incorrect Control Flow Implementation).

Attackers can exploit this vulnerability remotely over the network with no privileges or user interaction required. By sending a HEAD request to a route protected by GET middleware—such as authentication or validation checks—an attacker bypasses those middleware entirely while triggering execution of the target GET handler. This enables unauthorized access or manipulation of application logic, leading to high integrity impacts without compromising confidentiality or availability.

The NestJS security advisory (GHSA-wf42-42fg-fg84) and related GitHub resources detail the fix implemented in version 11.1.16, with a subsequent release at v11.1.17. Practitioners should upgrade to NestJS 11.1.16 or later to mitigate the issue, as evidenced by the patching commit cbdf737cd6e7cefa52d05ecea2ae4af95c464614.

EU & UK References

Vulnerability Data

Nest is a framework for building scalable Node.js server-side applications. In versions 11.1.15 and below, 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…

more

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), and the actual handler will still be executed. This issue is fixed in version 11.1.16.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-40879Same product: Nestjs Nest
CVE-2025-69211Same product: Nestjs Nest
CVE-2023-26108Same product: Nestjs Nest
CVE-2026-35515Same product: Nestjs Nest
CVE-2024-29409Same product: Nestjs Nest
CVE-2026-2293Same product: Nestjs Nest
CVE-2025-54782Same vendor: Nestjs
CVE-2025-32996Shared CWE-670
CVE-2024-25622Shared CWE-670
CVE-2023-41058Shared CWE-670

Affected Assets

nestjs
nest
≤ 11.1.16

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.

Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect paths that deviate from intended logic.

prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References