critical · 9.1 Patched

Sentry-Javascript: Middleware Bypass when using Tunnel route

CVE-2026-114139 · GHSA-mchm-gjx6-7h55 · published 22 Oct 2026

How serious is it

  • Severity: critical, CVSS score 9.1 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-114139?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • @sentry/nextjs (npm) >= 9.36.0, < 9.47.2
  • @sentry/nextjs (npm) >= 10.0.0-alpha.0, < 10.75.2
  • @sentry/nextjs (npm) >= 11.0.0-alpha.0, < 11.0.0-rc.1

How to check

  1. Run npm ls @sentry/nextjs in your project to see the installed version, including copies pulled in by other packages.
  2. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
  3. Or run npx shippable-dev scan localhost:3000 in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. On >= 9.36.0, < 9.47.2: Upgrade @sentry/nextjs to 9.47.2 or later, commit the lockfile and redeploy.
  2. On >= 10.0.0-alpha.0, < 10.75.2: Upgrade @sentry/nextjs to 10.75.2 or later, commit the lockfile and redeploy.
  3. On >= 11.0.0-alpha.0, < 11.0.0-rc.1: Upgrade @sentry/nextjs to 11.0.0-rc.1 or later, commit the lockfile and redeploy.
  4. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

### 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.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities