CVE-2026-2293
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe @nestjs/platform-fastify adapter in NestJS has a path-normalization vulnerability that can allow attackers to bypass authentication and authorization middleware. When Fastify's path-normalization options are enabled, certain path variations may not be properly normalized before middleware execution, allowing unauthorized access to protected routes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 11.1.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if @nestjs/platform-fastify is in useReview package.json for @nestjs/platform-fastify dependency, or run 'npm list @nestjs/platform-fastify' to list installed packagesAffected if The package is present in the project dependencies
-
Confirm the installed NestJS versionRun 'npm list @nestjs/core' or 'npm list @nestjs/common' to display the installed NestJS versionAffected if Version is 11.1.13 exactly
-
Verify Fastify is the application adapterCheck the main.ts bootstrap function for use of NestFactory.create or NestFactory.createAsync with @nestjs/platform-fastify, such as 'import { FastifyAdapter } from @nestjs/platform-fastify'Affected if FastifyAdapter or Fastify is used as the NestJS platform adapter
-
Inspect Fastify adapter path-normalization configurationSearch for FastifyAdapter instantiation in bootstrap code and check for options like 'normalizePath' or path-related configuration passed to the adapter or Fastify server instanceAffected if Custom path-normalization or path-handling options are configured in the Fastify adapter setup
-
Determine if authentication middleware protects routesReview the application for use of @UseGuards, AuthGuard, or custom middleware that guards protected endpoints, and identify which routes are protectedAffected if Authentication or authorization middleware is configured to guard certain routes
A user is affected if using @nestjs/platform-fastify with NestJS version 11.1.13 and has authentication middleware protecting routes, as path-normalization could allow bypass of those protections.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade NestJS to the latest version that addresses this vulnerability, or review and adjust Fastify path-normalization configuration to ensure all request paths are properly normalized before reaching authentication/authorization middleware.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data