{"answers":{"affected":"2 open source packages ship an affected version, including @nestjs/platform-fastify.","exploited":"There is no known exploitation of CVE-2026-54281 in the wild and no public exploit code.","fix":"Upgrade @nestjs/platform-fastify to 11.1.24 or later.","what":"CVE-2026-54281 is a high-severity authentication bypass vulnerability in nestjs nest, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54281 and fix it if it is affected.\n\nWhat it is: CVE-2026-54281 is a high-severity authentication bypass vulnerability in nestjs nest, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54281 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @nestjs/platform-fastify (npm): affected all versions; fixed in 11.1.24\n- @nestjs/platform-fastify (npm): affected all versions; fixed in 11.1.24\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54281/ (Markdown: https://insights.sbomify.com/CVE-2026-54281/index.md)","id":"CVE-2026-54281","markdown":"https://insights.sbomify.com/CVE-2026-54281/index.md","name":"CVE-2026-54281","record":{"aliases":["GHSA-6v32-fjc9-9qf6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NestJS Fastify adapter","requires_auth":"low_privilege","summary":"Attackers can bypass authentication middleware in NestJS Fastify applications by appending a trailing slash to URLs, allowing unauthorized access to protected routes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nest: Middleware Bypass on Fastify via Trailing Slash","id":"CVE-2026-54281","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Starlette: Unvalidated request path concatenated into authority poisons request.url.hostname","id":"CVE-2026-54282"},"packages":[{"ecosystem":"npm","fixed":["11.1.24"],"introduced":["0"],"last_affected":[],"package":"@nestjs/platform-fastify","purl":null,"source":"GHSA-6v32-fjc9-9qf6"},{"ecosystem":"npm","fixed":["11.1.24"],"introduced":["0"],"last_affected":[],"package":"@nestjs/platform-fastify","purl":"pkg:npm/%40nestjs/platform-fastify","source":"GHSA-6v32-fjc9-9qf6"}],"prev":{"headline":"AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect","id":"CVE-2026-54280"},"products":["nest"],"published":"2026-06-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nestjs"]},"summary":"Attackers can bypass authentication middleware in NestJS Fastify applications by appending a trailing slash to URLs, allowing unauthorized access to protected routes.","url":"https://insights.sbomify.com/CVE-2026-54281/"}