{"answers":{"affected":"4 open source packages ship an affected version, including fastify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41919 in the wild and no public exploit code.","fix":"Upgrade fastify to a fixed version for your release line: 3.29.4 or 4.10.2.","what":"CVE-2022-41919 is a medium-severity vulnerability in fastify, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-41919 and fix it if it is affected.\n\nWhat it is: CVE-2022-41919 is a medium-severity vulnerability in fastify, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-41919 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fastify (npm): affected from 3.0.0; fixed in 3.29.4\n- fastify (npm): affected from 3.0.0; fixed in 3.29.4\n- fastify (npm): affected from 4.0.0; fixed in 4.10.2\n- fastify (npm): affected from 4.0.0; fixed in 4.10.2\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-2022-41919/ (Markdown: https://insights.sbomify.com/CVE-2022-41919/index.md)","id":"CVE-2022-41919","markdown":"https://insights.sbomify.com/CVE-2022-41919/index.md","name":"CVE-2022-41919","record":{"aliases":["GHSA-3fjj-p79j-c9hh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js web framework","requires_auth":"none","summary":"Attackers can bypass CORS protections and perform CSRF attacks by using specific content types in fetch requests against Fastify routes.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fastify","vendor":"fastify"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Fastify is a web framework with minimal overhead and plugin architecture. The attacker can use the incorrect `Content-Type` to bypass the `Pre-Flight` checking of `fetch`. `fetch()` requests with Content-Type’s essence as \"application/x-www-form-urlencoded\", \"multipart/form-data\", or \"text/plain\", could potentially be used to invoke routes that only accepts `application/json` content type, thus bypassing any CORS protection, and therefore they could lead to a Cross-Site Request Forgery attack. This issue has been patched in version 4.10.2 and 3.29.4. As a workaround, implement Cross-Site Request Forgery protection using `@fastify/csrf'.","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":"Fastify vulnerable to Cross-Site Request Forgery (CSRF) attack via incorrect content type","id":"CVE-2022-41919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":4,"n_references":3,"next":{"headline":"Zip slip in Lancet","id":"CVE-2022-41920"},"packages":[{"ecosystem":"npm","fixed":["3.29.4"],"introduced":["3.0.0"],"last_affected":[],"package":"fastify","purl":null,"source":"GHSA-3fjj-p79j-c9hh"},{"ecosystem":"npm","fixed":["3.29.4"],"introduced":["3.0.0"],"last_affected":[],"package":"fastify","purl":"pkg:npm/fastify","source":"GHSA-3fjj-p79j-c9hh"},{"ecosystem":"npm","fixed":["4.10.2"],"introduced":["4.0.0"],"last_affected":[],"package":"fastify","purl":null,"source":"GHSA-3fjj-p79j-c9hh"},{"ecosystem":"npm","fixed":["4.10.2"],"introduced":["4.0.0"],"last_affected":[],"package":"fastify","purl":"pkg:npm/fastify","source":"GHSA-3fjj-p79j-c9hh"}],"prev":{"headline":"Issue with fine-grained access control of indices backing data streams","id":"CVE-2022-41918"},"products":["fastify"],"published":"2022-11-22","related":[{"cvss_score":8.1,"headline":"fastify vulnerable to request body replacement via an async validation result collision","id":"CVE-2026-84504","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers","id":"CVE-2026-76169","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to header validation bypass via incomplete schema case normalization","id":"CVE-2026-84428","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to request validation bypass via skipped boolean false schemas","id":"CVE-2026-84469","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header","id":"CVE-2026-33806","kev_date_added":null,"published":"2026-04-15"},{"cvss_score":7.5,"headline":"Fastify's Content-Type header tab character allows body validation bypass","id":"CVE-2026-25223","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":7.5,"headline":"Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass","id":"CVE-2025-32442","kev_date_added":null,"published":"2025-04-18"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["fastify"]},"summary":"Attackers can bypass CORS protections and perform CSRF attacks by using specific content types in fetch requests against Fastify routes.","url":"https://insights.sbomify.com/CVE-2022-41919/"}