{"answers":{"affected":"6 open source packages ship an affected version, including @sentry/nextjs.","exploited":"There is no known exploitation of CVE-2026-114139 in the wild and no public exploit code.","fix":"Upgrade @sentry/nextjs to a fixed version for your release line: 10.75.2, 11.0.0-rc.1 or 9.47.2.","what":"CVE-2026-114139 is a critical vulnerability in getsentry sentry-javascript, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114139 and fix it if it is affected.\n\nWhat it is: CVE-2026-114139 is a critical vulnerability in getsentry sentry-javascript, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-114139 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @sentry/nextjs (npm): affected from 10.0.0-alpha.0; fixed in 10.75.2\n- @sentry/nextjs (npm): affected from 10.0.0-alpha.0; fixed in 10.75.2\n- @sentry/nextjs (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-rc.1\n- @sentry/nextjs (npm): affected from 11.0.0-alpha.0; fixed in 11.0.0-rc.1\n- @sentry/nextjs (npm): affected from 9.36.0; fixed in 9.47.2\n- @sentry/nextjs (npm): affected from 9.36.0; fixed in 9.47.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-114139/ (Markdown: https://insights.sbomify.com/CVE-2026-114139/index.md)","id":"CVE-2026-114139","markdown":"https://insights.sbomify.com/CVE-2026-114139/index.md","name":"CVE-2026-114139","record":{"aliases":["ECHO-bc46-68ba-ff1a","GHSA-mchm-gjx6-7h55"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Sentry-Javascript: Middleware Bypass when using Tunnel route","id":"CVE-2026-114139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":6,"n_references":10,"next":{"headline":"nbconvert: File write via path traversal in cell output filenames","id":"CVE-2026-114140"},"packages":[{"ecosystem":"npm","fixed":["10.75.2"],"introduced":["10.0.0-alpha.0"],"last_affected":[],"package":"@sentry/nextjs","purl":null,"source":"GHSA-mchm-gjx6-7h55"},{"ecosystem":"npm","fixed":["10.75.2"],"introduced":["10.0.0-alpha.0"],"last_affected":[],"package":"@sentry/nextjs","purl":"pkg:npm/%40sentry/nextjs","source":"GHSA-mchm-gjx6-7h55"},{"ecosystem":"npm","fixed":["11.0.0-rc.1"],"introduced":["11.0.0-alpha.0"],"last_affected":[],"package":"@sentry/nextjs","purl":null,"source":"GHSA-mchm-gjx6-7h55"},{"ecosystem":"npm","fixed":["11.0.0-rc.1"],"introduced":["11.0.0-alpha.0"],"last_affected":[],"package":"@sentry/nextjs","purl":"pkg:npm/%40sentry/nextjs","source":"GHSA-mchm-gjx6-7h55"},{"ecosystem":"npm","fixed":["9.47.2"],"introduced":["9.36.0"],"last_affected":[],"package":"@sentry/nextjs","purl":null,"source":"GHSA-mchm-gjx6-7h55"},{"ecosystem":"npm","fixed":["9.47.2"],"introduced":["9.36.0"],"last_affected":[],"package":"@sentry/nextjs","purl":"pkg:npm/%40sentry/nextjs","source":"GHSA-mchm-gjx6-7h55"}],"prev":{"headline":"Django REST framework: Accept header with many large quoted parameters burns ~19s of CPU per request in content negotiation","id":"CVE-2026-114138"},"products":["sentry-javascript"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["getsentry"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114139/"}