chore(deps): update dependency @nestjs/platform-fastify to v12.0.2 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nestjs/platform-fastify (source)	12.0.1 → 12.0.2

---

@​nestjs/platform-fastify: Path-scoped middleware bypass via absolute-form request targets

GHSA-9c5c-9qcx-q35q

More information

Details

Field	Value
Ecosystem	npm
Package	@nestjs/platform-fastify
Affected versions	>= 12.0.0, < 12.0.2 and < 11.2.4
Patched versions	12.0.2 and 11.2.4 (upgrade to 12.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.1
instead of GET /path HTTP/1.1) reaches the route handler without running the path-scoped Nest middleware bound to
that route. Applications that enforce authentication or authorization in middleware execute the protected handler
with those checks skipped.

Impact

Any application that

• uses @nestjs/platform-fastify, and
• binds middleware to specific paths via MiddlewareConsumer.forRoutes(...) or .exclude(...), and
• is reachable by a client that controls the raw request line.

Node'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 handler
is dispatched normally. Two places on the middleware side matched against the raw request target instead:

1. The bundled copy of the @fastify/middie engine at packages/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.
2. FastifyAdapter's own re-check in createMiddlewareFactory(), which tests the middleware path regexp against
   req.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 version
constraint), Fastify did not reflect the deprecated top-level router options (ignoreTrailingSlash,
ignoreDuplicateSlashes, caseSensitive, useSemicolonDelimiter) in initialConfig.routerOptions, which is what
the 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

@Controller('users')
export class UsersController {
  @Get()
  findAll() {
    return 'protected data';
  }
}

@Module({ controllers: [UsersController] })
export class AppModule implements NestModule {
  configure(consumer: MiddlewareConsumer) {
    consumer
      .apply((req, res) => res.end('blocked by auth middleware'))
      .forRoutes({ path: 'users', method: RequestMethod.GET });
  }
}

supertest and light-my-request always emit origin-form targets, so the request has to be written to the socket:

const { connect } = require('node:net');

const socket = connect(3000, '127.0.0.1', () => {
  socket.write(
    'GET http://127.0.0.1:3000/users HTTP/1.1\r\n' +
      'Host: 127.0.0.1:3000\r\n' +
      'Connection: close\r\n\r\n',
  );
});
socket.pipe(process.stdout);

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.

• The bundled @fastify/middie fork was removed and the package now depends on @fastify/middie@9.3.4, which
  resolves absolute-form targets before matching.
• The adapter resolves absolute-form targets in its own route check, mirroring find-my-way.
• Deprecated top-level Fastify router options are folded into routerOptions so the middleware engine and the
  router 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
onRequest hook, and confirm with the request above that the rejection takes effect:

const adapter = new FastifyAdapter();
adapter.getInstance().addHook('onRequest', (request, reply, done) => {
  const target = request.raw.url ?? '';
  // "*" is the legitimate request target of "OPTIONS * HTTP/1.1"
  if (target[0] !== '/' && target !== '*') {
    reply.code(400).send();
    return;
  }
  done();
});

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 Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

References

• https://github.com/fastify/middie/security/advisories/GHSA-hx87-8wv7-pjv8
• https://github.com/nestjs/nest/security/advisories/GHSA-9c5c-9qcx-q35q
• https://github.com/nestjs/nest/pull/17737
• https://github.com/nestjs/nest/commit/5226fe084cf64b357de436f154bc89f2d319b621
• https://github.com/nestjs/nest/commit/dda252090ecb65009d9ff366444303796fc44fd7
• https://github.com/nestjs/nest/releases/tag/v11.2.4
• https://github.com/nestjs/nest/releases/tag/v12.0.2
• https://github.com/advisories/GHSA-9c5c-9qcx-q35q

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

nestjs/nest (@​nestjs/platform-fastify)

v12.0.2

Compare Source

v12.0.2 (2026-09-14)

Bug fixes

• platform-socket.io, platform-ws
  • #​17666 fix(socket.io): keep the message stream alive when a handler throws (@​hktitof)
• microservices
  • #​17728 fix(microservices): detach signal listeners of connected microservices (@​kamilmysliwiec)
  • #​17671 fix(microservices): fail requests whose reply subscription is rejected (@​samuelmbabhazi)
  • #​17670 fix(microservices): do not treat foreign JSON as an RPC envelope (@​xia-chao)
  • #​17644 fix(microservices): don't flatten plain handler results with pre-request hooks (@​iamolegga)
  • #​17641 fix(microservices): run the mqtt listen callback once (@​johnnyhuirilef)
• common
  • #​17710 fix(common): collapse duplicate internal slashes in normalizePath (@​Asadshah7950)
  • #​17655 fix(common): validate UUID v3 variant (@​gwagjiug)
  • #​17702 fix(common): treat empty string as array input in ParseArrayPipe (@​xia-chao)
• core
  • #​17667 fix(core): discover factory providers with discovery decorators (@​hktitof)
  • #​17709 fix(core): avoid treating error instances with statusCode as http errors (@​Asadshah7950)
  • #​17625 fix(core): clean up repeated shutdown signal listeners (@​Raj4478)
• platform-fastify
  • #​17705 fix(fastify): derive neutral version when accept header is absent (@​Gaurav1112)
  • #​17699 fix(fastify): send responses for exceptions thrown from middleware (@​micalevisk)

Enhancements

• microservices
  • #​17734 feat(microservices): add maxConnectionAttempts to ServerMqtt (@​kamilmysliwiec)

Dependencies

• platform-fastify
  • #​17729 fix(deps): update dependency fastify to v5.12.4 (@​renovate[bot])

Committers: 16

• Abdellatif Anaflous (@​hktitof)
• Alexey Solovyov (@​lyohaplotinka)
• Asad Ali Shah (@​Asadshah7950)
• Gyeonghun Park (@​Gyeonghun-Park)
• Johnny J. Huirilef Millán (@​johnnyhuirilef)
• Kamil Mysliwiec (@​kamilmysliwiec)
• Kumar Gaurav (@​Gaurav1112)
• Micael Levi L. Cavalcante (@​micalevisk)
• Ming (@​MingLin1995)
• Mohammed Said (@​Se3do)
• Rajeshwar Singh (@​Raj4478)
• Xia Chao (@​xia-chao)
• @​iamolegga
• cui fliter (@​cuishuang)
• samuel mbabhazi (@​samuelmbabhazi)
• 곽지욱 (@​gwagjiug)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.