cve.bz

CVE-2026-114139 getsentry sentry-javascript: Protection Mechanism Failure

9.1 criticalEPSS 0.5%Fix available

Critical (9.1) in getsentry sentry-javascript. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @sentry/nextjs 10.75.2, 11.0.0-rc.1, 9.47.2.

On this page
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.

Severity

CVSS 4.0

9.1 critical
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
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @sentry/nextjs (npm): fixed in 9.47.2, 10.75.2, 11.0.0-rc.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-114139 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114139?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114139?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114139 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
getsentry sentry-javascript>= 9.36.0, < 9.47.2
getsentry sentry-javascript>= 10.0.0-alpha.0, < 10.75.2
getsentry sentry-javascript>= 11.0.0-alpha.0, < 11.0.0-rc.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mchm-gjx6-7h55npm@sentry/nextjs>=9.36.0 <9.47.29.47.2
GHSA-mchm-gjx6-7h55npm@sentry/nextjs>=10.0.0-alpha.0 <10.75.210.75.2
GHSA-mchm-gjx6-7h55npm@sentry/nextjs>=11.0.0-alpha.0 <11.0.0-rc.111.0.0-rc.1

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON