Vulnerability Description
Jupyter Server is the backend for Jupyter web applications. From 2.0.0 until 2.6.0, enabling GatewayClient.url replaced the normal KernelWebsocketHandler with WebSocketChannelsHandler, which authenticated the user but did not call authorizer.is_authorized(...) for the execute action on the kernels resource. A restricted authenticated user could therefore open an upstream kernel channel and obtain kernel execution despite the configured Authorizer denying that action, exposing data and credentials available to the kernel and permitting modification or disruption of the kernel environment. The default gateway configuration is fixed in version 2.6.0. In 2.6.0 and later, the same authorization bypass remains possible when a deployment manually registers the deprecated jupyter_server.gateway.handlers module, because its handler still omits the configured kernel-execute authorization decision.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/jupyter-server/jupyter_server/commit/35ffe5d435682128da16dc14
- https://github.com/jupyter-server/jupyter_server/pull/1261
- https://github.com/jupyter-server/jupyter_server/releases/tag/v2.6.0
- https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-354v-3
FAQ
What is CVE-2026-114135?
CVE-2026-114135 is a vulnerability with a CVSS score of 8.8 (HIGH). Jupyter Server is the backend for Jupyter web applications. From 2.0.0 until 2.6.0, enabling GatewayClient.url replaced the normal KernelWebsocketHandler with WebSocketChannelsHandler, which authentic...
How severe is CVE-2026-114135?
CVE-2026-114135 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-114135?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.