fix(deps): update dependency fastify to v5.8.3 [security]#1208
fix(deps): update dependency fastify to v5.8.3 [security]#1208renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
Deployment failed with the following error: Learn More: https://vercel.com/itman?upgradeToPro=build-rate-limit |
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
PR Summary
|
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to 5454d06 in 13 seconds. Click for details.
- Reviewed
13lines of code in1files - Skipped
1files when reviewing. - Skipped posting
0draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
Workflow ID: wflow_Td96RDSo65U0EN5M
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
5454d06 to
5b038d9
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
5b038d9 to
e80189e
Compare
e80189e to
127f336
Compare
This PR contains the following updates:
5.3.2→5.8.3Fastify Vulnerable to DoS via Unbounded Memory Allocation in sendWebStream
CVE-2026-25224 / GHSA-mrq3-vjjr-p77c
More information
Details
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:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Fastify's Content-Type header tab character allows body validation bypass
CVE-2026-25223 / GHSA-jx2c-rxcm-jvmq
More information
Details
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:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
fastify: request.protocol and request.host Spoofable via X-Forwarded-Proto/Host from Untrusted Connections
CVE-2026-3635 / GHSA-444r-cwp2-x5xf
More information
Details
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:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release 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: (UTC)
🚦 Automerge: Enabled.
♻ 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.