chore(deps): update dependency fastify to v5 [security]#11
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency fastify to v5 [security]#11renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
d60ca18 to
9f72d55
Compare
9f72d55 to
3b19bd0
Compare
3b19bd0 to
caaa401
Compare
caaa401 to
d5c2860
Compare
d5c2860 to
39e49cd
Compare
39e49cd to
2656ce2
Compare
2656ce2 to
d72a0a7
Compare
Contributor
Author
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
d72a0a7 to
8c32c16
Compare
Detected SAST Vulnerabilities |
8c32c16 to
d37c07a
Compare
d37c07a to
7327601
Compare
7327601 to
a2094f0
Compare
a2094f0 to
3194f51
Compare
e80f24b to
e185de2
Compare
b088bf9 to
98b8242
Compare
9f7472e to
e290308
Compare
e290308 to
525ed12
Compare
3e7ba90 to
c65238c
Compare
c65238c to
fdfc955
Compare
fdfc955 to
820eecf
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.3.0→^5.8.34.3.0→5.8.3GitHub 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
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVE-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
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NCVE-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
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NCVE-2026-25224
Impact
A Denial of Service vulnerability in Fastify’s Web Streams response handling can allow a remote client to exhaust server memory. Applications that return a
ReadableStream(orResponsewith a Web Stream body) viareply.send()are impacted. A slow or non-reading client can trigger unbounded buffering when backpressure is ignored, leading to process crashes or severe degradation.Patches
The issue is fixed in Fastify 5.7.3. Users should upgrade to 5.7.3 or later.
Workarounds
Avoid sending Web Streams from Fastify responses (e.g.,
ReadableStreamorResponsebodies). Use Node.js streams (stream.Readable) or buffered payloads instead until the project can upgrade.References
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LCVE-2026-3635
Summary
When
trustProxyis configured with a restrictive trust function (e.g., a specific IP liketrustProxy: '10.0.0.1', a subnet, a hop count, or a custom function), therequest.protocolandrequest.hostgetters readX-Forwarded-ProtoandX-Forwarded-Hostheaders from any connection — including connections from untrusted IPs. This allows an attacker connecting directly to Fastify (bypassing the proxy) to spoof both the protocol and host seen by the application.Affected Versions
fastify <= 5.8.2
Impact
Applications using
request.protocolorrequest.hostfor security decisions (HTTPS enforcement, secure cookie flags, CSRF origin checks, URL construction, host-based routing) are affected whentrustProxyis configured with a restrictive trust function.When
trustProxy: true(trust everything), bothhostandprotocoltrust all forwarded headers — this is expected behavior. The vulnerability only manifests with restrictive trust configurations.Severity
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NRelease Notes
fastify/fastify (fastify)
v5.8.3Compare Source
This fixes CVE CVE-2026-3635 GHSA-444r-cwp2-x5xf.
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.8.2...v5.8.3
v5.8.2Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.8.1...v5.8.2
v5.8.1Compare Source
Fixes "Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation": GHSA-573f-x89g-hqp9.
CVE-2026-3419
Full Changelog: fastify/fastify@v5.8.0...v5.8.1
v5.8.0Compare Source
What's Changed
tsconfig.eslint.jsonby @mrazauskas in #6524New Contributors
Full Changelog: fastify/fastify@v5.7.4...v5.8.0
v5.7.4Compare Source
Full Changelog: fastify/fastify@v5.7.3...v5.7.4
v5.7.3Compare Source
CVE-2026-25224.What's Changed
Full Changelog: fastify/fastify@v5.7.2...v5.7.3
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
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.