Repository navigation
chore(deps): update dependency @nestjs/platform-fastify to v11.2.4 [security] - #104
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
January 8, 2026 17:53
b06c352 to
34e4365
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
January 23, 2026 19:35
d1a4d2a to
879d6fd
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
February 2, 2026 14:46
879d6fd to
708b0ae
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
February 17, 2026 14:46
fa01786 to
33a63d8
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
March 13, 2026 18:14
33a63d8 to
8b109d4
Compare
renovate
Bot
deleted the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
March 27, 2026 04:55
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
March 30, 2026 17:44
8b109d4 to
30c47d1
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
April 8, 2026 17:27
30c47d1 to
25c58e9
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
April 29, 2026 18:04
25c58e9 to
08c216a
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
May 18, 2026 11:56
dea6b27 to
db8cf72
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
June 1, 2026 16:40
933a260 to
d54715f
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
June 11, 2026 19:37
d54715f to
e3483f3
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
July 16, 2026 17:00
b3a4676 to
4d27776
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
July 24, 2026 14:58
55aa264 to
a3ce0a6
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
July 30, 2026 15:36
a3ce0a6 to
e5c2824
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
August 12, 2026 00:09
e5c2824 to
3d1156e
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
August 26, 2026 11:55
3d1156e to
af6a3d9
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
September 8, 2026 00:22
ae2efde to
be5d6e9
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
September 21, 2026 11:55
be5d6e9 to
4d6bbcf
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
2 times, most recently
from
October 4, 2026 14:10
986e6da to
c3813dc
Compare
renovate
Bot
force-pushed
the
renovate/npm-nestjs-platform-fastify-vulnerability
branch
from
October 13, 2026 17:04
c3813dc to
d46c2d8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
11.1.6→11.2.4Nest has a Fastify URL Encoding Middleware Bypass (TOCTOU)
CVE-2025-69211 / GHSA-8wpr-639p-ccrj
More information
Details
A NestJS application is vulnerable if it meets all of the following criteria:
@nestjs/platform-fastify.NestMiddleware(viaMiddlewareConsumer) for security checks (authentication, authorization, etc.), or throughapp.use().forRoutes('admin')).Example Vulnerable Config:
Attack Vector:
/adminadminGET /%61dmin%61dmin), but controller for/adminis executed.Consequences:
Patches
Patched in
@nestjs/platform-fastify@11.1.11Resources
Credit goes to Hacktron AI for reporting this issue.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Nest has a Fastify URL Encoding Middleware Bypass
CVE-2026-2293 / GHSA-r4wm-x892-vjmx
More information
Details
Impact
What kind of vulnerability is it? Who is impacted?
A NestJS application using
@nestjs/platform-fastifycan allow bypass of any middleware when Fastify path-normalization options (e.g.,ignoreTrailingSlash,ignoreDuplicateSlashes,useSemicolonDelimiter) are enabled. In affected route-scoped middleware setups, variant paths may skip middleware checks while still reaching the protected handler.The bug is a path canonicalization mismatch between middleware matching and route matching in Nest’s Fastify adapter.
Nest passes Fastify routerOptions (such as
ignoreTrailingSlash,ignoreDuplicateSlashes,useSemicolonDelimiter) to the Fastify router in packages/platform-fastify/adapters/fastify-adapter.ts:253.But middleware execution is decided by a separate regex check over
req.originalUrlin packages/platform-fastify/adapters/fastify-adapter.ts:706 and packages/platform-fastify/adapters/fastify-adapter.ts:713.If that regex does not match, Nest does
next()and skips the middleware (packages/platform-fastify/adapters/fastify-adapter.ts:714), while Fastify may still normalize the same path and route it to the protected handler. So the vulnerability exists because security checks (middleware) and request dispatch(router) use different URL interpretations.This is a fail-open design issue (inconsistent normalization), not just a bad app config: non-default router options make the mismatch reachable.
Patches
Fixed in
@nestjs/platform-fastify@11.1.14References
Credit goes to Fluidattacks (Cristian Vargas) https://fluidattacks.com/advisories/neton
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Nest Fastify HEAD Request Middleware Bypass
CVE-2026-33011 / GHSA-wf42-42fg-fg84
More information
Details
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:
Patches
Fixed in
@nestjs/platform-fastify@11.1.16Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Nest: Middleware Bypass on Fastify via Trailing Slash
CVE-2026-54281 / GHSA-6v32-fjc9-9qf6
More information
Details
Impact
An authentication bypass vulnerability exists in
@nestjs/platform-fastify(confirmed on version11.1.24, the latest available release at time of report). When middleware is registered through NestJS'sMiddlewareConsumer.forRoutes()API on the Fastify adapter, an unauthenticated client can bypass the Nest middleware registered for that route by simply appending a trailing slash (/) to the request URL.This bypass works on the default Fastify adapter configuration — no special router options need to be enabled. Applications using the standard CRUD route shape (
GET /resourceandGET /resource/:id) are affected when they protect those routes withMiddlewareConsumer.forRoutes()middleware.Patches
Fixed in
@nestjs/platform-fastify@11.1.24References
Kudos goes to @a-tt-om
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
@nestjs/platform-fastify: Path-scoped middleware bypass via absolute-form request targets
GHSA-9c5c-9qcx-q35q
More information
Details
@nestjs/platform-fastify>= 12.0.0, < 12.0.2and< 11.2.412.0.2and11.2.4(upgrade to12.0.3/11.2.5)Summary
On the Fastify adapter, an HTTP request that uses an absolute-form request target (
GET http://host/path HTTP/1.1instead of
GET /path HTTP/1.1) reaches the route handler without running the path-scoped Nest middleware bound tothat route. Applications that enforce authentication or authorization in middleware execute the protected handler
with those checks skipped.
Impact
Any application that
@nestjs/platform-fastify, andMiddlewareConsumer.forRoutes(...)or.exclude(...), andNode's HTTP server accepts absolute-form targets, so no special server configuration is needed. Exposure is reduced
when a reverse proxy in front of the application rewrites the request target to origin-form, which most do.
Where the bypassed middleware performs authentication or authorization, the result is an authentication or
authorization bypass. Where it performs logging, rate limiting or body handling, those are silently skipped instead.
Details
Fastify's router (
find-my-way) resolves an absolute-form target to its path before matching, so the route handleris dispatched normally. Two places on the middleware side matched against the raw request target instead:
@fastify/middieengine atpackages/platform-fastify/adapters/middie/fastify-middie.ts.NestJS carried this fork to apply an earlier path-decoding fix and it did not track the upstream absolute-form fix
released in
@fastify/middie@9.3.4.FastifyAdapter's own re-check increateMiddlewareFactory(), which tests the middleware path regexp againstreq.originalUrl.Both normalized and percent-decoded the target, but neither resolved absolute-form to a path, so the router and the
middleware layer disagreed about which path was being requested.
A second, related defect contributed. Because the adapter always passes
routerOptions(to install the versionconstraint), Fastify did not reflect the deprecated top-level router options (
ignoreTrailingSlash,ignoreDuplicateSlashes,caseSensitive,useSemicolonDelimiter) ininitialConfig.routerOptions, which is whatthe middleware engine reads. Applications passing those options at the top level had middleware normalize paths
differently from the router, which widened the mismatch.
Proof of concept
supertestandlight-my-requestalways emit origin-form targets, so the request has to be written to the socket:Observed on an affected version:
protected data— the middleware did not run.Expected, and observed on a patched version:
blocked by auth middleware.Patches
Fixed in 12.0.2 and 11.2.4. Upgrading to 12.0.3 or 11.2.5 is recommended.
@fastify/middiefork was removed and the package now depends on@fastify/middie@9.3.4, whichresolves absolute-form targets before matching.
find-my-way.routerOptionsso the middleware engine and therouter normalize paths identically.
Workarounds
If you cannot upgrade, reject non-origin-form request targets before middleware runs. Register the hook on the
Fastify instance before the application is initialized, so that it runs ahead of the middleware engine's own
onRequesthook, and confirm with the request above that the rejection takes effect:Rejecting or normalizing absolute-form targets at a reverse proxy in front of the application is equally effective.
Credit
Reported by ZeroVuln Labs.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
nestjs/nest (@nestjs/platform-fastify)
v11.2.4Compare Source
What's changed
v11.2.3Compare Source
What's Changed
Full Changelog: nestjs/nest@v11.2.2...v11.2.3
v11.2.2Compare Source
What's changed
v11.2.1Compare Source
What's Changed
Full Changelog: nestjs/nest@v11.2.0...v11.2.1
v11.2.0Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/nest@v11.1.29...v11.2.0
v11.1.29Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/nest@v11.1.28...v11.1.29
v11.1.28Compare Source
v11.1.28 (2026-07-08)
Bug fixes
corecommonwebsocketsEnhancements
coreDependencies
platform-fastifyplatform-expressCommitters: 4
v11.1.27Compare Source
What's Changed
Full Changelog: nestjs/nest@v11.1.26...v11.1.27
v11.1.26Compare Source
What's Changed
Full Changelog: nestjs/nest@v11.1.25...v11.1.26
v11.1.25Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/nest@v11.1.24...v11.1.25
v11.1.24Compare Source
v11.1.24 (2026-05-25)
Bug fixes
coreEnhancements
coreDependencies
platform-wsCommitters: 2
v11.1.23Compare Source
v11.1.23 (2026-05-21)
Bug fixes
coreCommitters: 1
v11.1.22Compare Source
v11.1.22 (2026-05-21)
Bug fixes
coreEnhancements
coreCommitters: 2
v11.1.21Compare Source
v11.1.21 (2026-05-14)
Bug fixes
coreCommitters: 1
v11.1.20Compare Source
v11.1.20 (2026-05-13)
Bug fixes
core,testingcoremicroservicescommonplatform-socket.ioEnhancements
microservicescommonplatform-expressDependencies
platform-wsCommitters: 13
v11.1.19Compare Source
v11.1.19 (2026-04-13)
Bug fixes
microservicesCommitters: 2
v11.1.18Compare Source
v11.1.18 (2026-04-03)
Bug fixes
microservicescoreDependencies
core,platform-express,platform-fastifyplatform-fastifyplatform-wscommonCommitters: 6
v11.1.17Compare Source
v11.1.17 (2026-03-16)
Enhancements
microservicesBugs
platform-fastifycbdf737(@kamilmysliwiec)Dependencies
commonplatform-fastifyCommitters: 3
v11.1.16Compare Source
v11.1.16 (2026-03-05)
Bug fixes
microservicesDependencies
platform-expressCommitters: 2
v11.1.15Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/nest@v11.1.14...v11.1.15
v11.1.14Compare Source
v11.1.14 (2026-02-17)
Bug fixes
platform-fastifycommonEnhancements
commonCommitters: 5
v11.1.13Compare Source
v11.1.13 (2026-02-03)
Bug fixes
commonEnhancements
microservicescommonDependencies
platform-fastifyplatform-expressCommitters: 6
v11.1.12Compare Source
v11.1.12 (2026-01-15)
Bug fixes
commonDependencies
platform-wscommonplatform-fastifyCommitters: 3
v11.1.11Compare Source
v11.1.11 (2025-12-29)
Bug fixes
platform-fastifycoreDependencies
platform-socket.ioplatform-fastifycommonCommitters: 3
v11.1.10Compare Source
v11.1.10 (2025-12-22)
Bug fixes
coremicroservicescommonEnhancements
commoncoremicroservicescommon,coreDependencies
platform-fastifyplatform-expresscommonCommitters: 11
v11.1.9Compare Source
v11.1.9 (2025-11-14)
Bug fixes
coreEnhancements
commonDependencies
platform-fastifyCommitters: 4
v11.1.8Compare Source
v11.1.8 (2025-10-27)
Bug fixes
coreplatform-fastifyConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.