# CVE-2022-41919: Fastify vulnerable to Cross-Site Request Forgery (CSRF) attack via incorrect content type

> Attackers can bypass CORS protections and perform CSRF attacks by using specific content types in fetch requests against Fastify routes.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-3fjj-p79j-c9hh

## What is CVE-2022-41919?

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.

### Official 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'.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-41919?

4 open source packages ship an affected version, including fastify. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fastify` | npm | From 3.0.0 | 3.29.4 |
| `fastify` | npm | From 3.0.0 | 3.29.4 |
| `fastify` | npm | From 4.0.0 | 4.10.2 |
| `fastify` | npm | From 4.0.0 | 4.10.2 |

Products: Fastify Fastify.

## How do I fix CVE-2022-41919?

Upgrade fastify to a fixed version for your release line: 3.29.4 or 4.10.2.

## Is CVE-2022-41919 being exploited?

There is no known exploitation of CVE-2022-41919 in the wild and no public exploit code.

## Other vulnerabilities in fastify

- [CVE-2026-84504](https://insights.sbomify.com/CVE-2026-84504/): fastify vulnerable to request body replacement via an async validation result collision (high 8.1)
- [CVE-2026-76169](https://insights.sbomify.com/CVE-2026-76169/): fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers (high 7.5)
- [CVE-2026-84428](https://insights.sbomify.com/CVE-2026-84428/): fastify vulnerable to header validation bypass via incomplete schema case normalization (high 7.5)
- [CVE-2026-84469](https://insights.sbomify.com/CVE-2026-84469/): fastify vulnerable to request validation bypass via skipped boolean false schemas (high 7.5)
- [CVE-2026-33806](https://insights.sbomify.com/CVE-2026-33806/): fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41919 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2022-41919 in the wild and no public exploit code.

Affected packages and fixed versions:
- fastify (npm): affected from 3.0.0; fixed in 3.29.4
- fastify (npm): affected from 3.0.0; fixed in 3.29.4
- fastify (npm): affected from 4.0.0; fixed in 4.10.2
- fastify (npm): affected from 4.0.0; fixed in 4.10.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41919/ (Markdown: https://insights.sbomify.com/CVE-2022-41919/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41919
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41919
- OSV: https://osv.dev/vulnerability/CVE-2022-41919

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41919/
Summaries are generated and may contain mistakes; the official description above is the record.