nestjs nest up to 11.1.15 GET control flow

Summaryinfo

A vulnerability was found in nestjs nest up to 11.1.15. It has been classified as critical. Affected is an unknown function of the component GET Handler. Performing a manipulation results in control flow. This vulnerability is reported as CVE-2026-33011. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, was found in nestjs nest up to 11.1.15. This affects an unknown code block of the component GET Handler. The manipulation with an unknown input leads to a control flow vulnerability. CWE is classifying the issue as CWE-670. The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33011 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 11.1.16 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch cbdf737cd6e7cefa52d05ecea2ae4af95c464614 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• nestjs

Name

• nest

Version

• 11.1.0
• 11.1.1
• 11.1.2
• 11.1.3
• 11.1.4
• 11.1.5
• 11.1.6
• 11.1.7
• 11.1.8
• 11.1.9
• 11.1.10
• 11.1.11
• 11.1.12
• 11.1.13
• 11.1.14
• 11.1.15

License

• open-source

Website

• Product: https://github.com/nestjs/nest/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion