fix(deps): update dependency fastify to v5.8.1 [security]#706
Merged
Conversation
Contributor
NPM Publishing labels 🏷️🔵 This PR has the |
dskloetc
approved these changes
Mar 6, 2026
Contributor
|
🚀 Successfully created version bump PR: #707 |
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
1 participant
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.7.4→5.8.1GitHub Vulnerability Alerts
CVE-2026-3419
Description
Fastify incorrectly accepts malformed
Content-Typeheaders containing trailing characters after the subtype token, in violation of RFC 9110 §8.3.1. For example, a request sent withContent-Type: application/json garbagepasses validation and is processed normally, rather than being rejected with415 Unsupported Media Type.When regex-based content-type parsers are in use (a documented Fastify feature), the malformed value is matched against registered parsers using the full string including the trailing garbage. This means a request with an invalid content-type may be routed to and processed by a parser it should never have reached.
Impact
An attacker can send requests with RFC-invalid
Content-Typeheaders that bypass validity checks, reach content-type parser matching, and be processed by the server. Requests that should be rejected at the validation stage are instead handled as if the content-type were valid.Workarounds
Deploy a WAF rule to protect against this
Fix
The fix is available starting with v5.8.1.
Release Notes
fastify/fastify (fastify)
v5.8.1Compare Source
v5.8.0Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 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.