CVE-2026-2293: NestJS 11.1.13 - Lack of data validation allowing authentication/authorization bypass
A NestJS application using @nestjs/platform-fastify can allow bypass of authentication/authorization middleware when Fastify path-normalization options are enabled.
This issue affects nest.Js: 11.1.13.
Security readout for executives and security teams
Plain-English summary
NestJS 11.1.13 applications using the Fastify platform can mishandle normalized paths in a way that bypasses authentication or authorization middleware. The business risk is unauthorized access to protected application functions or data where the affected configuration is present.
Executive priority
Treat as high priority for internet-facing NestJS APIs because the outcome is authorization bypass, not just denial of service. Scope first: affected version, Fastify adapter, and path-normalization configuration determine urgency.
Technical view
CVE-2026-2293 affects NestJS 11.1.13 with @nestjs/platform-fastify when Fastify path-normalization options are enabled. The issue is described as missing data validation leading to authentication/authorization bypass, mapped to CWE-551 and CWE-863, with CVSS 4.0 score 8.2.
Likely exposure
Exposure appears limited to NestJS 11.1.13 applications using @nestjs/platform-fastify with relevant Fastify path-normalization options enabled. The bundle lists default status as unaffected outside the named version, but organizations should verify dependency lockfiles and runtime configuration.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is network-reachable, low-complexity, requires no privileges or user interaction, but has an attack requirement tied to specific path-normalization configuration.
Researcher notes
Evidence supports a specific affected release and configuration-dependent auth bypass. The source bundle names v11.1.14 as a patch reference, but does not include full exploit details or proof of active exploitation. Avoid assuming all NestJS versions or adapters are affected.
Mitigation direction
Upgrade affected NestJS 11.1.13 deployments using the vendor v11.1.14 patch reference.
Review Fastify path-normalization settings in NestJS services using @nestjs/platform-fastify.
Check vendor and distribution advisories for environment-specific remediation guidance.
Prioritize externally exposed applications with authentication or authorization middleware.
Add regression tests for protected routes under configured path-normalization behavior.
Validation and detection
Inventory package-lock, pnpm-lock, yarn.lock, or SBOM entries for NestJS 11.1.13.
Identify services using @nestjs/platform-fastify rather than other NestJS HTTP platforms.
Confirm whether Fastify path-normalization options are enabled in application bootstrap code.
Review protected route tests for authorization enforcement under normalized path handling.
Verify production deployments are upgraded beyond the affected release.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-551: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-551 · source CWE mapping
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.