Open
Conversation
ad37c2d to
d03e7d7
Compare
d03e7d7 to
1631858
Compare
1631858 to
7646222
Compare
7646222 to
1e79e89
Compare
1e79e89 to
15f380b
Compare
15f380b to
94ef381
Compare
8c16b67 to
602c1c2
Compare
602c1c2 to
5d47652
Compare
562ab32 to
399f0c1
Compare
399f0c1 to
0d3d5cf
Compare
0d3d5cf to
f920122
Compare
f920122 to
1432d11
Compare
af4b909 to
2c9e150
Compare
2c9e150 to
15a7916
Compare
d09ce25 to
f83459b
Compare
abf2738 to
7e20b19
Compare
7e20b19 to
bb4d2f3
Compare
bb4d2f3 to
5246efa
Compare
5246efa to
6e2ddac
Compare
6e2ddac to
d89bee9
Compare
d89bee9 to
31ea73e
Compare
31ea73e to
ed1008b
Compare
ed1008b to
13a68a6
Compare
13a68a6 to
97fc443
Compare
97fc443 to
e519389
Compare
e519389 to
365a736
Compare
365a736 to
84c6984
Compare
84c6984 to
ce0e8a0
Compare
ce0e8a0 to
09e992b
Compare
09e992b to
9f6f2d6
Compare
9f6f2d6 to
b25c47b
Compare
b25c47b to
b26dc66
Compare
b26dc66 to
4b2ef64
Compare
a1edb27 to
7c19eab
Compare
7c19eab to
27dc8ed
Compare
27dc8ed to
95cf067
Compare
95cf067 to
73b0b4f
Compare
6aac200 to
5423cb2
Compare
5423cb2 to
e4b1e54
Compare
e4b1e54 to
f8b253f
Compare
f8b253f to
3fbcfa8
Compare
3fbcfa8 to
12e3fd5
Compare
12e3fd5 to
45b56d7
Compare
45b56d7 to
897dde6
Compare
897dde6 to
791a1a2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.1.0→^5.0.0GitHub Vulnerability Alerts
CVE-2022-39288
Impact
An attacker can send an invalid
Content-Typeheader that can cause the application to crash, leading to a possible Denial of Service attack. Only the v4.x line is affected.(This was updated: upon a close inspection, v3.x is not affected after all).
Patches
Yes, update to
> v4.8.0.Workarounds
You can reject the malicious content types before the body parser enters in action.
References
See the HackerOne report #1715536
For more information
Fastify security policy
CVE-2022-41919
Impact
The attacker can use the incorrect
Content-Typeto bypass thePre-Flightchecking offetch.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 acceptsapplication/jsoncontent type, thus bypassing any CORS protection, and therefore they could lead to a Cross-Site Request Forgery attack.Patches
For
4.xusers, please update to at least4.10.2For
3.xusers, please update to at least3.29.4Workarounds
Implement Cross-Site Request Forgery protection using
@fastify/csrf.References
Check out the HackerOne report: https://hackerone.com/reports/1763832.
For more information
Fastify security policy
CVE-2026-25223
Impact
A validation bypass vulnerability exists in Fastify where request body validation schemas specified by Content-Type can be completely circumvented. By appending a tab character (
\t) followed by arbitrary content to the Content-Type header, attackers can bypass body validation while the server still processes the body as the original content type.For example, a request with
Content-Type: application/json\tawill bypass JSON schema validation but still be parsed as JSON.This vulnerability affects all Fastify users who rely on Content-Type-based body validation schemas to enforce data integrity or security constraints. The concrete impact depends on the handler implementation and the level of trust placed in the validated request body, but at the library level, this allows complete bypass of body validation for any handler using Content-Type-discriminated schemas.
This issue is a regression or missed edge case from the fix for a previously reported vulnerability.
Patches
This vulnerability has been patched in Fastify v5.7.2. All users should upgrade to this version or later immediately.
Workarounds
If upgrading is not immediately possible, user can implement a custom
onRequesthook to reject requests containing tab characters in the Content-Type header:Resources
Release Notes
fastify/fastify (fastify)
v5.7.2Compare Source
Parsing of the
content-typeheader has been improved to a strict parser in PR #6414. This means only header values in the form described in RFC 9110 are accepted.What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.7.1...v5.7.2
v5.7.1Compare Source
What's Changed
Full Changelog: fastify/fastify@v5.7.0...v5.7.1
v5.7.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.6.2...v5.7.0
v5.6.2Compare Source
v5.6.1Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.6.0...v5.6.1
v5.6.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.5.0...v5.6.0
v5.5.0Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.4.0...v5.5.0
v5.4.0Compare Source
What's Changed
Full Changelog: fastify/fastify@v5.3.3...v5.4.0
v5.3.3Compare Source
What's Changed
setErrorHandleroverriding a previously defined error handler on an encapsulated context by @jean-michelet in #6097fastify-diagnostics-channelby @inyourtime in #6117New Contributors
Full Changelog: fastify/fastify@v5.3.2...v5.3.3
v5.3.2Compare Source
Unfortunately, v5.3.1 did not include a complete fix for "Invalid content-type parsing could lead to validation bypass" and CVE-2025-32442. This is a follow-up patch to cover an edge case.
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.3.1...v5.3.2
v5.3.1Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.3.0...v5.3.1
v5.3.0Compare Source
What's Changed
[kState].readyPromisefor garbage collection by @LiviaMedeiros in #6030New Contributors
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.