Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

Sentry-Javascript: Middleware Bypass when using Tunnel routeGHSA-mchm-gjx6-7h55

Fix: getsentry/sentry-javascript#24499

GHSA-mchm-gjx6-7h55 is a CWE-693 vulnerability in @sentry/nextjs. A fix is available for @sentry/nextjs — see the affected versions and patch details below.

Also known asCVE-2026-114139
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

150other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@sentry/nextjsnpm
7.8Mdownloads / week

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npm@sentry/nextjs≥ 9.36.0&&< 9.47.29.47.2npm install @sentry/nextjs@9.47.2
📦npm@sentry/nextjs≥ 10.0.0-alpha.0&&< 10.75.210.75.2npm install @sentry/nextjs@10.75.2
📦npm@sentry/nextjs≥ 11.0.0-alpha.0&&< 11.0.0-rc.111.0.0-rc.1npm install @sentry/nextjs@11.0.0-rc.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/nextjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @sentry/nextjs to 9.47.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mchm-gjx6-7h55 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 midd
O3 Security · Impact-Aware SCA

Is GHSA-mchm-gjx6-7h55 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Sentry-Javascript: Middleware Bypass when using Tunnel…