@Sentry/Nextjs (>= 10.0.0-Alpha.0, < 10.75.2) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/@sentry/nextjs--10.0.0-alpha.0--10.75.2/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioThu, 22 Oct 2026 20:00:27 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSentry-Javascript: Middleware bypass via tunnelRoute (CVE-2026-114139)https://feed.craftedsignal.io/briefs/2026-10-sentry-middleware-bypass/Thu, 22 Oct 2026 20:00:27 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-sentry-middleware-bypass/A middleware bypass vulnerability in the @sentry/nextjs SDK allows unauthenticated access to routes if the configured tunnel path overlaps with application routes in Webpack-based builds.The @sentry/nextjs SDK contains a middleware bypass vulnerability (CVE-2026-114139) affecting Webpack-based builds when the tunnelRoute option is configured. The SDK is designed to forward browser events to a specific path (the tunnel) while skipping middleware to prevent request rejection. However, the logic incorrectly skips middleware for all requests under the tunnel path, not just those intended for Sentry. If an application route resolves under the configured tunnel path, and that route relies exclusively on middleware for authorization, an attacker can bypass these checks. Sentry services and organization data are not affected.

Impact

Successful exploitation allows unauthorized access to application routes that rely solely on middleware for authorization. Impact is limited to routes that overlap with the tunnelRoute path. Access to the route is not granted additional privileges; routes with internal server-side session validation remain protected.

Recommendation

  • Upgrade @sentry/nextjs to version 9.47.2, 10.75.2, or 11.0.0-rc.1 or later to apply the patch that restricts middleware skipping to the specific tunnel rewrite.
  • If immediate patching is not possible, modify the tunnelRoute configuration to a path that does not collide with existing application routes.
  • Enforce authorization checks within the route handlers, layouts, or data-access layers in addition to middleware, following a defense-in-depth approach.
  • Transition to Turbopack for builds, as it is not affected by this specific implementation flaw.
]]>criticaladvisoryweb-applicationmiddleware-bypasscve-2026-114139