Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 272/272 feeds/APIs · 469/469 docs · 9/9 advisories · checked 16:14 UTC Customize Public modeDiscuss ChangeIntel on Discord

Sentry-Javascript: Middleware Bypass when using Tunnel route

Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.

osv · GHSA-mchm-gjx6-7h55

Published

### 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](https://github.com/getsentry/sentry-javascript/releases/tag/9.47.2), [10.75.2](https://github.com/getsentry/sentry-javascript/releases/tag/10.75.2) and [11.0.0-rc.1](https://github.com/getsentry/sentry-javascript/releases/tag/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.

Source published
22 Oct 2026 15:55:07 UTC
Source modified
22 Oct 2026 16:00:09 UTC
Observed here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V4 · 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

Publisher rating · CRITICAL

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 31 Oct 16:14 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current