Repository navigation
⬆️(dependencies) update @sentry/nextjs to v10.75.2 [SECURITY] - #2901
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
|
Size Change: -1 B (0%) Total Size: 4.09 MB 📦 View Changed
|
This branch has not been deployed
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:
10.75.0→10.75.2Sentry-Javascript: Middleware Bypass when using Tunnel route
CVE-2026-114139 / GHSA-mchm-gjx6-7h55
More information
Details
Impact
The
tunnelRouteoption makes the SDK send browser events to a path on your own Next.js server (for example/monitoring), where a rewrite forwards them to Sentry to prevent ad blockers from blocking them. To keep those envelope requests from being rejected by your middleware, the SDK skips middleware for them.The middleware skip was wider than the rewrite. The rewrite only serves requests to the tunnel path itself with the
oandpparameters set. The skip applied to anything under the tunnel path. Requests in that gap go to your application instead of Sentry, and your middleware never runs on them.Skipping middleware does not grant the request any privileges. Routes that check the session server-side are still protected.
You are affected only if all of the following are true:
tunnelRouteis set (a string path ortrue),/monitoring/foowithtunnelRoute: '/monitoring') or a dynamic segment at the route root (app/[locale]/…), which matches any first path segment, andSentry's own services, and the data in your Sentry organization, are not affected.
Patches
Fixed in 9.47.2, 10.75.2 and 11.0.0-rc.1. The skip now matches only the requests the tunnel rewrite actually serves. No configuration change is needed.
Workarounds
tunnelRouteto a path no route of yours can resolve under, or remove the option.next buildfrom Next.js 16).Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v10.75.2Compare Source
dataCollection.urlQueryParamsto collected URLs and query strings (#24572)v10.75.1Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.