How severe is CVE-2026-114139?

No CVSS score has been assigned to CVE-2026-114139 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-114139?

CVE-2026-114139 affects the following packages: @sentry/nextjs (npm), @sentry/nextjs (npm), @sentry/nextjs (npm). Ecosystems affected: npm.

How do I fix CVE-2026-114139?

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

How do I detect CVE-2026-114139 in my npm dependencies?

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.

How do I mitigate CVE-2026-114139 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-114139 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-114139 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-114139?

CVE-2026-114139 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-114139?

CVE-2026-114139 is classified as CWE-693 (CWE-693). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-114139 published, and has it been updated?

CVE-2026-114139 was published on October 21, 2026 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-114139 — @sentry/nextjs

Fix: getsentry/sentry-javascript@878b685

CVE-2026-114139 is a CWE-693 vulnerability in @sentry/nextjs. A fix is available for @sentry/nextjs — see the affected versions and patch details below.

Sentry-Javascript: Middleware Bypass when using Tunnel route

Also known asGHSA-mchm-gjx6-7h55

Published

Oct 21, 2026

Updated

Oct 22, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 22, 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

📦@sentry/nextjs📦@sentry/nextjs📦@sentry/nextjs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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:

tunnelRoute is set (a string path or true),
your app is built with webpack (Turbopack builds are not affected),
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
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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sentry/nextjs`	≥ 9.36.0&&< 9.47.2	9.47.2`npm install @sentry/nextjs@9.47.2`
📦npm	`@sentry/nextjs`	≥ 10.0.0-alpha.0&&< 10.75.2	10.75.2`npm install @sentry/nextjs@10.75.2`
📦npm	`@sentry/nextjs`	≥ 11.0.0-alpha.0&&< 11.0.0-rc.1	11.0.0-rc.1`npm install @sentry/nextjs@11.0.0-rc.1`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update @sentry/nextjs to 9.47.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-114139 is resolved across your whole dependency graph.
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