CVE-2026-114135
published 2026-10-21CVE-2026-114135: 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…
PriorityP359high8.8CVSS 3.1
AVNACLPRLUINSUCHIHAH
EPSS
0.39%
31.5th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | jupyter-server | >= 2.0.0 < 2.6.0 | 2.6.0 |
| jupyter-server | jupyter_server | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization
ghsa·2026-10-22
CVE-2026-114135 [HIGH] CWE-862 Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization
Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization
### Summary
Jupyter Server's gateway WebSocket handler checks that a user is authenticated, but it does not ask the configured Authorizer whether that user may execute kernels.
In Jupyter Server 2.0.0 through 2.5.0, enabling GatewayClient.url automatically replaced the normal kernel channel handler with this gateway-specific handler. An authenticated user who is denied the `execute` action on the `kernels` resource can therefore still open a kernel channel and send messages to the upstream kernel.
### Details
The normal handler performs the expected authorization check before creating the WebSocket connection:
https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/services/kernels/web
VulDB
Jupyter Server up to 2.5.x GatewayClient GatewayClient.url is_authorized authorization (EUVD-2026-107544)
vuldb·2026-10-21·CVSS 8.8
CVE-2026-114135 [HIGH] Jupyter Server up to 2.5.x GatewayClient GatewayClient.url is_authorized authorization (EUVD-2026-107544)
A vulnerability, which was classified as critical, was found in Jupyter Server up to 2.5.x. Affected by this issue is the function is_authorized of the file GatewayClient.url of the component GatewayClient. The manipulation results in authorization bypass.
This vulnerability is identified as CVE-2026-114135. The attack can be executed remotely. There is not any exploit available.
You should upgrade the affected component.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/jupyter-server/jupyter_server/commit/35ffe5d435682128da16dc144a8e9e9f8fa85dd8https://github.com/jupyter-server/jupyter_server/pull/1261https://github.com/jupyter-server/jupyter_server/releases/tag/v2.6.0https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-354v-3q48-cv69
2026-10-21
Published