No attacks reportedCVE published · 21 Oct 2026
@sentry/nextjs
CVE-2026-114139 Severity · Critical
CVSS 9.1
Affected
9.36.0 to 9.47.1, 10.0.0-alpha.0 to 10.75.1, 11.0.0-alpha.0 to 11.0.0-rc.0
Fixed in
9.47.2, 10.75.2, 11.0.0-rc.1

CVE alert · Node.js and JavaScript

CVE-2026-114139: the Sentry SDK for Next.js can let strangers skip checks done only in middleware

A flaw in the Sentry library for Next.js lets anyone open routes under its tunnel path that only middleware (the code that checks logins first) protects. It needs Sentry's tunnelRoute option and webpack (a code packaging tool). Update @sentry/nextjs to 9.47.2, 10.75.2 or 11.0.0-rc.1 today.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-114139 in @sentry/nextjs, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-114139-sentry-nextjs/

What the alert says (facts checked 23 October 2026):
- Affected: 9.36.0 to 9.47.1, 10.0.0-alpha.0 to 10.75.1, 11.0.0-alpha.0 to 11.0.0-rc.0
- Fixed in: 9.47.2, 10.75.2, 11.0.0-rc.1
- Exploited: No attacks reported as of 23 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where @sentry/nextjs runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    npm ls @sentry/nextjs

    npm ls next

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
Product@sentry/nextjs (Sentry SDK for Next.js, npm package)
Affected versions9.36.0 to 9.47.1, 10.0.0-alpha.0 to 10.75.1, 11.0.0-alpha.0 to 11.0.0-rc.0
Fixed in9.47.2, 10.75.2, 11.0.0-rc.1
Severity9.1 Critical (CVSS 4.0, GitHub)
Who can attackAnyone over the network, no login needed, if the app sets tunnelRoute, builds with webpack, has a route under the tunnel path and checks logins only in middleware
ExploitedNo attacks reported as of 23 October 2026
CVE published21 October 2026

What an attacker can do

Many Next.js apps use middleware to check that the visitor is logged in. The Sentry SDK (the library that reports your app's errors) has an option called tunnelRoute. It is a path on your own server that forwards these error reports, so ad blockers do not drop them. With webpack builds, the SDK skips your middleware for every request under that path. Sentry's tunnel only serves one exact address, so every other request under the path reaches your own routes unchecked.

A stranger with no account can open routes you thought were private. They can read or change whatever those routes expose, such as customer data or admin settings. Routes that also check the login on the server stay protected. Sentry's own services and the error data you store with them are not affected.

Who is affected

The flaw is in @sentry/nextjs versions 9.36.0 to 9.47.1, 10.0.0-alpha.0 to 10.75.1, and 11.0.0-alpha.0 to 11.0.0-rc.0. Your app is exposed only when all four conditions below are true.

  1. tunnelRoute is set, either as a path such as '/monitoring' or as true.
  2. The app is built with webpack. Builds made with Turbopack (the other Next.js build tool, the default for next build from version 16) are not affected.
  3. One of your routes falls under the tunnel path. This can be a direct clash, such as /monitoring/foo with tunnelRoute set to '/monitoring'. It can also come from a dynamic segment at the root of the app (a folder such as app/[locale]/ that matches any first part of a URL).
  4. Middleware is the only code that checks whether the user is allowed in on those routes.

GitHub rated it 9.1 Critical on CVSS 4.0 (a 0 to 10 scale for how serious a flaw is). Sentry's own advisory, public since 24 September 2026, labels it Moderate.

How to check your version

In the app's project folder, run this command:

shell
npm ls @sentry/nextjs

If the version is in one of the ranges listed under "Who is affected", keep going.

Then open your Next.js config file: next.config.js, next.config.mjs or next.config.ts. Look for tunnelRoute in the options passed to withSentryConfig. If it is absent, the app is not exposed.

Check the Next.js version too:

shell
npm ls next

From version 16, next build uses Turbopack by default, and those builds are not affected. On an older version, or if you build with webpack, keep going.

Last, look for routes under your tunnel path and for a root dynamic segment such as app/[locale]/. For each match, see whether any code besides middleware confirms that the user is allowed in.

What to do now

Update @sentry/nextjs today:

  • version 9: 9.47.2 or later
  • version 10: 10.75.2 or later
  • version 11: 11.0.0-rc.1 or later

On 23 October 2026, the newest release on npm was 11.9.0 for version 11, and the fix itself for version 9. To move a version 10 app to its newest release, run:

shell
npm install @sentry/nextjs@10.76.2

You do not need to change the configuration. Rebuild and redeploy the app so the fixed version runs in production.

If you cannot update yet, Sentry gives these workarounds:

  • Set tunnelRoute to a path that none of your routes can fall under, or remove the option.
  • Build with Turbopack.
  • Repeat the login check in the route, layout or data-access code, as well as in middleware.

Sentry has not published signs of compromise. In your server logs, look for requests under the tunnel path that reached a private route. Normal requests go only to the exact tunnel address, with o= and p= values in the URL. As of 23 October 2026, nobody has publicly reported an attack.

Get help

Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.

Web app and API security test

A penetration test of your web app and its API: who can see whose data, and what an attacker can change.

From AED 20,000, excl. 5% VAT

Ask for a quote Book a call

Sources

  1. CVE-2026-114139 record CVE Program
  2. GHSA-mchm-gjx6-7h55 repository security advisory Sentry (getsentry/sentry-javascript)
  3. fix(nextjs): Align tunnel request matching in middleware with tunnel rewrite (PR #24499) Sentry (getsentry/sentry-javascript)
  4. Next.js build options (tunnelRoute) Sentry Docs
  5. Known Exploited Vulnerabilities Catalog CISA

More CVE alerts

All CVE alerts