deps(deps): update dependency fastify to v5.12.1 [security] - #140
Open
renovate[bot] wants to merge 1 commit into
Open
deps(deps): update dependency fastify to v5.12.1 [security]#140renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
April 18, 2025 20:51
b77204f to
fae915f
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
September 25, 2025 17:13
fae915f to
3e39026
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
October 21, 2025 19:37
3e39026 to
1265e02
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
November 18, 2025 23:28
1265e02 to
d523f47
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
December 3, 2025 16:48
d523f47 to
a8edee9
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
February 3, 2026 02:49
a8edee9 to
01e7486
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
February 12, 2026 12:54
01e7486 to
c89a816
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
2 times, most recently
from
March 25, 2026 22:50
364ef26 to
d3879cf
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
March 31, 2026 10:01
d3879cf to
31031d5
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
2 times, most recently
from
April 27, 2026 20:41
31031d5 to
c036e8f
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
2 times, most recently
from
May 18, 2026 13:14
fe23aa5 to
88c5b80
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
June 1, 2026 19:14
88c5b80 to
eebacf3
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
3 times, most recently
from
July 14, 2026 09:12
8c7a9e7 to
9df1614
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
2 times, most recently
from
July 14, 2026 09:18
693592b to
8a197ca
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
July 30, 2026 19:18
8a197ca to
6f584ec
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
August 12, 2026 02:48
6f584ec to
5f5a7d6
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
August 26, 2026 10:01
5f5a7d6 to
e5b68c7
Compare
renovate
Bot
force-pushed
the
renovate/npm-fastify-vulnerability
branch
from
September 3, 2026 00:50
e5b68c7 to
2f67e1e
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:
5.0.0→5.12.1Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass
CVE-2025-32442 / GHSA-mg2h-6x62-wpwc
More information
Details
Impact
In applications that specify different validation strategies for different content types, it's possible to bypass the validation by providing a slightly altered content type such as with different casing or altered whitespacing before
;.Users using the the following pattern are affected:
User using the following pattern are not affected:
Patches
This was patched in v5.3.1, but unfortunately it did not cover all problems. This has been fully patched in v5.3.2.
Version v4.9.0 was also affected by this issue. This has been fully patched in v4.9.1.
Workarounds
Do not specify multiple content types in the schema.
References
Are there any links users can visit to find out more?
https://hackerone.com/reports/3087928
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 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).
fastify vulnerable to schema validation bypass via root primitive coercion mismatch
CVE-2026-18504 / GHSA-w2qp-rph6-63g4
More information
Details
Impact
fastifybefore 5.12.1, when a route uses a root-level primitive body schema (for example an integer with a minimum and maximum) and the default type coercion, validates the coerced value but exposes the original, uncoerced value to the route handler. For example, a JSON body"10"is coerced to the number10and passes an integer 1 to 10 schema, butrequest.bodystays the string"10". An application that trusts the validated type is handed a value that did not satisfy the schema, which can bypass limits the application enforces on that typed value. Object and array body schemas are not affected, they coerce their members in place.Patches
Upgrade to
fastify5.12.1.Workarounds
Until you can upgrade, avoid relying on the validated type of a root primitive body. Wrap the value in an object schema (object properties are coerced in place), for example accept
{ "value": 10 }and readrequest.body.value, or re-check the type in the handler.Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
fastify/fastify (fastify)
v5.12.1Compare Source
What's Changed
Full Changelog: fastify/fastify@v5.12.0...v5.12.1
v5.12.0Compare Source
What's Changed
Reply.prototype.mediaTypeby @github-actions[bot] in #6946undefinedfor invalid media types by @github-actions[bot] in #6947Full Changelog: fastify/fastify@v5.11.3...v5.12.0
v5.11.3Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.11.2...v5.11.3
v5.11.2Compare Source
v5.11.1Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.11.0...v5.11.1
v5.11.0Compare Source
What's Changed
Content-Typeparameter values by @aquie00t in #6865New Contributors
Full Changelog: fastify/fastify@v5.10.0...v5.11.0
v5.10.0Compare Source
v5.9.0Compare Source
What's Changed
findwithsomeinhasKeyfor correct boolean semantics by @aquie00t in #6759AssertionErrorwithFST_ERR_PLUGIN_DEPENDENCY_NOT_REGISTEREDincheckDependenciesby @aquie00t in #6774New Contributors
Full Changelog: fastify/fastify@v5.8.5...v5.9.0
v5.8.5Compare Source
This fixes CVE CVE-2026-33806 GHSA-247c-9743-5963.
What's Changed
New Contributors
Full Changelog: fastify/fastify@v5.8.4...v5.8.5
v5.8.4Compare Source
Full Changelog: fastify/fastify@v5.8.3...v5.8.4
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
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.