CVE-2026-114139Critical· 9.1▾ MidnightSentry-Javascript: Middleware Bypass when using Tunnel route
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 50.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 23.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
0.4%
0.4% → 0.5%
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),/monitoring/foo with tunnelRoute: '/monitoring') or a dynamic segment at the route root (app/[locale]/…), which matches any first path segment, andSentry's own services, and the data in your Sentry organization, are not affected.
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.
tunnelRoute to a path no route of yours can resolve under, or remove the option.next build from Next.js 16).@sentry/nextjs >= 9.36.0, < 9.47.2@sentry/nextjs >= 10.0.0-alpha.0, < 10.75.2@sentry/nextjs >= 11.0.0-alpha.0, < 11.0.0-rc.1Upgrade to a patched release:
@sentry/nextjs 9.47.2@sentry/nextjs 10.75.2@sentry/nextjs 11.0.0-rc.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-21400Medium· 6.7Protection mechanism failure for some Intel(R) AI Reference Models before version v3.4.1 within Ring 3: User Applications may allow an escalation of privilege
CVE-2021-47935High· 8.8Sentry 8.2.0 contains a remote code execution vulnerability that allows authenticated superusers to execute arbitrary commands by injecting malicious pickle-serialized objects through the audit log entry data parameter
CVE-2026-28757Medium· 6.7Protection mechanism failure for some Intel(R) Workload Services Framework software within Ring 3: User Applications may allow an escalation of privilege
CVE-2026-24693Medium· 6.7Protection mechanism failure for some Intel(R) oneCCL Bindings for PyTorch before version v2.8.0 within Ring 3: User Applications may allow an escalation of privilege
CVE-2026-101899Medium· 6.9Axios is a promise-based HTTP client for the browser and Node.js
CVE-2026-102673High· 8.2Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS