How severe is GHSA-6v32-fjc9-9qf6?

No CVSS score has been assigned to GHSA-6v32-fjc9-9qf6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6v32-fjc9-9qf6?

GHSA-6v32-fjc9-9qf6 affects the following packages: @nestjs/platform-fastify (npm). Ecosystems affected: npm.

How do I fix GHSA-6v32-fjc9-9qf6?

Update @nestjs/platform-fastify to 11.1.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6v32-fjc9-9qf6 is resolved across your whole dependency graph.

How do I detect GHSA-6v32-fjc9-9qf6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nestjs/platform-fastify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6v32-fjc9-9qf6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6v32-fjc9-9qf6?

O3 pinpoints whether GHSA-6v32-fjc9-9qf6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6v32-fjc9-9qf6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6v32-fjc9-9qf6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6v32-fjc9-9qf6 published, and has it been updated?

GHSA-6v32-fjc9-9qf6 was published on June 15, 2026 and was last updated on July 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-6v32-fjc9-9qf6

GHSA-6v32-fjc9-9qf6 is a security vulnerability in @nestjs/platform-fastify. O3 Security confirms whether GHSA-6v32-fjc9-9qf6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Nest: Middleware Bypass on Fastify via Trailing Slash

Also known asCVE-2026-54281

Published

Jun 15, 2026

Updated

Jul 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 18, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@nestjs/platform-fastify

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An authentication bypass vulnerability exists in @nestjs/platform-fastify (confirmed on version 11.1.24, the latest available release at time of report). When middleware is registered through NestJS's MiddlewareConsumer.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 /resource and GET /resource/:id) are affected when they protect those routes with MiddlewareConsumer.forRoutes() middleware.

Patches

Fixed in @nestjs/[email protected]

References

Kudos goes to @a-tt-om

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@nestjs/platform-fastify`	all versions	11.1.24

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nestjs/platform-fastify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @nestjs/platform-fastify to 11.1.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6v32-fjc9-9qf6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6v32-fjc9-9qf6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6v32-fjc9-9qf6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An authentication bypass vulnerability exists in `@nestjs/platform-fastify` (confirmed on version `11.1.24`, the latest available release at time of report). When middleware is registered through NestJS's `MiddlewareConsumer.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 /reso

O3 Security · Impact-Aware SCA

Is GHSA-6v32-fjc9-9qf6 in your dependencies?

O3 detects GHSA-6v32-fjc9-9qf6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works