CVE-2026-114139 json
Sentry-Javascript: Middleware Bypass when using Tunnel route
published 19d ago modified 13d ago also EUVD-2026-107549 , GHSA-mchm-gjx6-7h55
- cvss
- 9.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Sentry-Javascript is an official Sentry SDKs for JavaScript. From 9.36.0 until 9.47.2, 10.75.2, and 11.0.0-rc.1, the webpack integration for @sentry/nextjs skips application middleware for every request path under a configured tunnelRoute, while the tunnel rewrite serves only the exact tunnel path with valid o and p query parameters. When an application route directly collides with the tunnel path or a root dynamic segment resolves under it, an unauthenticated request can reach that route without middleware authorization. Exploitation requires tunnelRoute, a webpack build, a colliding route, and middleware being the only authorization control. This issue is fixed in versions 9.47.2, 10.75.2, and 11.0.0-rc.1.
Patch / fix
- npm @sentry/nextjs 9.47.2, 10.75.2, 11.0.0-rc.1
- sentry astro 9.47.2, 10.75.2, 11.0.0-rc.1
- sentry sentry_software_development_kit 9.47.2, 10.75.2, 11.0.0-rc.1
- github.com/getsentry/sentry-javascript@878b685 commit
- github.com/getsentry/sentry-javascript@c122aac commit
- github.com/getsentry/sentry-javascript@d525a2f commit
- github.com/getsentry/sentry-javascript#24499 pull request
- github.com/getsentry/sentry-javascript#24565 pull request
- github.com/getsentry/sentry-javascript#24760 pull request
- github.com/getsentry/sentry-javascript/releases/tag/10.75.2 release
- github.com/getsentry/sentry-javascript/releases/tag/11.0.0-rc.1 release
- github.com/getsentry/sentry-javascript/releases/tag/9.47.2 release
Is CVE-2026-114139 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 13d ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 9.1 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @sentry/nextjs | >=9.36.0, <9.47.2 >=10.0.0-alpha.0, <10.75.2 >=11.0.0-alpha.0, <11.0.0-rc.1 |
9.47.2 10.75.2 11.0.0-rc.1 |
Affected products
- getsentry sentry-javascript
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
github.com
/getsentry/sentry-javascript/pull/24499
web
-
github.com
/getsentry/sentry-javascript/pull/24565
web
-
github.com
/getsentry/sentry-javascript/pull/24760
web
-
github.com
/getsentry/sentry-javascript/commit/878b685c85dc12045e47e1932c96f5381d7ac532
web
-
github.com
/getsentry/sentry-javascript/commit/c122aac4f29541eb6da494296822c91eab3cf5ae
web
-
github.com
/getsentry/sentry-javascript/commit/d525a2f6015b47384bc139c30d58e0d5435d52e5
web
-
github.com
/getsentry/sentry-javascript/security/advisories/GHSA-mchm-gjx6-7h55
web
-
github.com
/getsentry/sentry-javascript/releases/tag/10.75.2
web
-
github.com
/getsentry/sentry-javascript/releases/tag/11.0.0-rc.1
web
-
github.com
/getsentry/sentry-javascript/releases/tag/9.47.2
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-114139
advisory
-
github.com
/getsentry/sentry-javascript
package
Sources
- CVE List CVE-2026-114139
- GitHub Advisory GHSA-mchm-gjx6-7h55
- NVD CVE-2026-114139
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.