Authorization Flaw in @nestjs/platform-fastify (CVE-2026-54281)
Summary
Vulnerability in @nestjs/platform-fastify (CVE-2026-54281). Risk of unauthorized operations or information disclosure. Exploitable via GET /resource. Mitigation: upgrade to 11.1.24 or later.
Original description
The description as published by the source.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.1.24, an authentication bypass vulnerability exists in @nestjs/platform-fastify. 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. This vulnerability is fixed in 11.1.24.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54281 has been found in @nestjs/platform-fastify.
Attackers can target a specific entry point like GET /resource over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @nestjs/platform-fastify to 11.1.24 or later.
If unsure, ask your IT team or search "@nestjs/platform-fastify CVE-2026-54281" on the vendor's site.
CVE-2026-54281 (@nestjs/platform-fastify) — CWE-863
Attack surface: GET /resource / GET /resource/
Patched: 11.1.24 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in @nestjs/platform-fastify. Attackers reach the vulnerable code path via GET /resource.
Check the vendor advisory for the affected versions of @nestjs/platform-fastify. Attack surface: GET /resource / GET /resource/.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 11.1.24.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /resource requests with malformed payloads or SQL meta-characters. Run grep -r '@nestjs/platform-fastify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@nestjs/platform-fastify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@nestjs/platform-fastifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /resource' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /resourceへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @nestjs/platform-fastify to 11.1.24ステージング環境で 11.1.24 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /resource on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com