{"answers":{"affected":"2 open source packages ship an affected version, including @nestjs/platform-fastify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33011 in the wild and no public exploit code.","fix":"Upgrade @nestjs/platform-fastify to 11.1.16 or later.","what":"CVE-2026-33011 is a high-severity vulnerability in nestjs nest, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33011 and fix it if it is affected.\n\nWhat it is: CVE-2026-33011 is a high-severity vulnerability in nestjs nest, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33011 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.16\n- @nestjs/platform-fastify (npm): affected all versions; fixed in 11.1.16\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-33011/ (Markdown: https://insights.sbomify.com/CVE-2026-33011/index.md)","id":"CVE-2026-33011","markdown":"https://insights.sbomify.com/CVE-2026-33011/index.md","name":"CVE-2026-33011","record":{"aliases":["GHSA-wf42-42fg-fg84"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NestJS framework","requires_auth":"none","summary":"Attackers can bypass GET middleware in NestJS Fastify applications by sending HEAD requests, potentially skipping security checks while executing handlers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nest","vendor":"nestjs"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"Nest is a framework for building scalable Node.js server-side applications. In versions 11.1.15 and below, 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: middleware will be completely skipped, the HTTP response won't include a body (since the response is truncated when redirecting a HEAD request to a GET handler), and the actual handler will still be executed. This issue is fixed in version 11.1.16.","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 Fastify HEAD Request Middleware Bypass","id":"CVE-2026-33011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Micronaut Framework vulnerable to a Denial of Service in HTML error response caching","id":"CVE-2026-33012"},"packages":[{"ecosystem":"npm","fixed":["11.1.16"],"introduced":["0"],"last_affected":[],"package":"@nestjs/platform-fastify","purl":null,"source":"GHSA-wf42-42fg-fg84"},{"ecosystem":"npm","fixed":["11.1.16"],"introduced":["0"],"last_affected":[],"package":"@nestjs/platform-fastify","purl":"pkg:npm/%40nestjs/platform-fastify","source":"GHSA-wf42-42fg-fg84"}],"prev":{"headline":"mcp-memory-service's Wildcard CORS with Credentials Enables Cross-Origin Memory Theft","id":"CVE-2026-33010"},"products":["nest"],"published":"2026-03-20","related":[{"cvss_score":8.2,"headline":"NestJS 11.1.13 - Lack of data validation allowing authentication/authorization bypass","id":"CVE-2026-2293","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":7.5,"headline":"Nest: DoS via Recursive handleData in JsonSocket (TCP Transport)","id":"CVE-2026-40879","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":6.9,"headline":"Nest has a Fastify URL Encoding Middleware Bypass (TOCTOU)","id":"CVE-2025-69211","kev_date_added":null,"published":"2025-12-29"},{"cvss_score":6.3,"headline":"@nestjs/core Improperly Neutralizes Special Elements in Output Used by a Downstream Component ('Injection')","id":"CVE-2026-35515","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.5,"headline":"nest allows a remote attacker to execute arbitrary code via the Content-Type header","id":"CVE-2024-29409","kev_date_added":null,"published":"2025-03-14"},{"cvss_score":3.7,"headline":"@nestjs/core vulnerable to Information Exposure via StreamableFile pipe","id":"CVE-2023-26108","kev_date_added":null,"published":"2023-03-06"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-20","vendors":["nestjs"]},"summary":"Attackers can bypass GET middleware in NestJS Fastify applications by sending HEAD requests, potentially skipping security checks while executing handlers.","url":"https://insights.sbomify.com/CVE-2026-33011/"}