chore(deps): update dependency @fastify/middie to v9.2.0 [security]#429
Merged
renovate[bot] merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
0ca8740 to
b81d5d0
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:
9.1.0→9.2.0GitHub Vulnerability Alerts
CVE-2026-2880
Summary
A path normalization inconsistency in
@fastify/middiecan result in authentication/authorization bypass when using path-scoped middleware (for example,app.use('/secret', auth)).When Fastify router normalization options are enabled (such as
ignoreDuplicateSlashes,useSemicolonDelimiter, and related trailing-slash behavior), crafted request paths may bypass middleware checks while still being routed to protected handlers.Impact
An unauthenticated remote attacker can access endpoints intended to be protected by middleware-based auth/authorization controls by sending specially crafted URL paths (for example,
//secretor/secret;foo=bar), depending on router option configuration.This may lead to unauthorized access to protected functionality and data exposure.
Affected versions
@fastify/middie@9.1.0Patched versions
Details
The issue is caused by canonicalization drift between:
@fastify/middiepath matching forapp.use('/prefix', ...), andBecause middleware and router did not always evaluate the same normalized path, auth middleware could be skipped while route resolution still succeeded.
Workarounds
Until patched version is deployed:
Resources
Credits
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NRelease Notes
fastify/middie (@fastify/middie)
v9.2.0Compare Source
Fixes GHSA-8p85-9qpw-fwgw
What's Changed
New Contributors
Full Changelog: fastify/middie@v9.1.0...v9.2.0
Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 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.