GitHub Advisoryadvisory · npm
GHSA-mchm-gjx6-7h55 Sentry-Javascript: Middleware Bypass when using Tunnel route
CRITICAL
Official page ↗
- Aliases
- CVE-2026-114139
- Ecosystem
- npm
- Packages
- @sentry/nextjs
- Severity
- Critical
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Weaknesses
- CWE-693
- Reviewed
- 2026-10-22
Affected packages
• npm @sentry/nextjs: >= 9.36.0, < 9.47.2 → fixed in 9.47.2
• npm @sentry/nextjs: >= 10.0.0-alpha.0, < 10.75.2 → fixed in 10.75.2
• npm @sentry/nextjs: >= 11.0.0-alpha.0, < 11.0.0-rc.1 → fixed in 11.0.0-rc.1
Description
Impact
The `tunnelRoute` option 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 `o` and `p` parameters 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:
1. `tunnelRoute` is set (a string path or `true`),
2. your app is built with webpack (Turbopack builds are not affected),
3. some route of your application resolves under the tunnel path. That could be a direct collision (`/monitoring/foo` with `tunnelRoute: '/monitoring'`) or a dynamic segment at the route root (`app/[locale]/…`), which matches any first path segment, and
4. your middleware is the only place that enforces authorization for those routes.
Sentry'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
• Set `tunnelRoute` to a path no route of yours can resolve under, or remove the option.
• Build with Turbopack (default for `next build` from Next.js 16).
• Enforce authorization in the route, layout or data-access path as well as in middleware.
Related
Alias · CVE (1)
- CVE-2026-114139 Sentry-Javascript is an official Sentry SDKs for JavaScript. vulnerability
Weakness · CWE (1)
- CWE-693 Protection Mechanism Failure weakness
References
- https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-mchm-gjx6-7h55 web
- https://nvd.nist.gov/vuln/detail/CVE-2026-114139 advisory
- https://github.com/getsentry/sentry-javascript/pull/24499 web
- https://github.com/getsentry/sentry-javascript/pull/24565 web
- https://github.com/getsentry/sentry-javascript/pull/24760 web
- https://github.com/getsentry/sentry-javascript/commit/878b685c85dc12045e47e1932c96f5381d7ac532 web
- https://github.com/getsentry/sentry-javascript/commit/c122aac4f29541eb6da494296822c91eab3cf5ae web
- https://github.com/getsentry/sentry-javascript/commit/d525a2f6015b47384bc139c30d58e0d5435d52e5 web
- https://github.com/getsentry/sentry-javascript package
- https://github.com/getsentry/sentry-javascript/releases/tag/10.75.2 web
- https://github.com/getsentry/sentry-javascript/releases/tag/11.0.0-rc.1 web
- https://github.com/getsentry/sentry-javascript/releases/tag/9.47.2 web