1218 matches found
CLEANSTART-2026-AU40449 jupyter-server is the backend for Jupyter web applications
Security vulnerability affects the jupyter-server package. jupyter-server is the backend for Jupyter web applications...
CLEANSTART-2026-CB37570 jupyter-server is the backend for Jupyter web applications
Security vulnerability affects the jupyter-server package. jupyter-server is the backend for Jupyter web applications...
CLEANSTART-2026-HP00250 Jupyter Server is the backend for Jupyter web applications
Security vulnerability affects the jupyter-server package. Jupyter Server is the backend for Jupyter web applications...
susvibes-jupyter-server-cve-2026-35397
SusVibes Benchmark Task: Jupyter Server Contents Path Resolution This repository contains one complete SusVibes-style benchmark task built from a real upstream Python security fix in Jupyter Server. The task is designed to evaluate whether an agent can reimplement masked contents path-resolution...
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...
Linux Distros Unpatched Vulnerability : CVE-2026-114135
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - 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...
SUSE CVE-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 WebSocketChannelsHandler, which authenticated the user but did not call authorizer.isauthorized... for the execute action on the kernels...
EUVD-2026-107544
Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization...
cadpr (>=0.1.0, <=0.1.1), cfnow (>=0.0.1, <=0.0.6) +19 more potentially affected by CVE-2026-114135 via jupyter-server (>=2.0.1, <=2.5.0)
jupyter-server PYPI version =2.0.1, =0.1.0, =0.0.1, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =0.3.0, =0.1.2, =0.1.3, =0.0.83, =0.2.13 and more Source cves: CVE-2026-114135 Source advisory: SNYK:PYTHON-JUPYTERSERVER-21431473...
Missing Authorization
Overview Affected versions of this package are vulnerable to Missing Authorization in the gateway handlers, where gateway-specific kernel and kernelspec endpoints are registered separately from the standard server handlers. An authenticated low-privileged user can send requests to gateway-proxied...
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...
GHSA-354V-3Q48-CV69 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...
cadpr (>=0.1.0, <=0.1.1), cfnow (>=0.0.1, <=0.0.6) +19 more potentially affected by CVE-2026-114135 via jupyter-server (>=2.0.1, <=2.5.0)
jupyter-server PYPI version =2.0.1, =0.1.0, =0.0.1, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =0.3.0, =0.1.2, =0.1.3, =0.0.83, =0.2.13 and more Source cves: CVE-2026-114135 Source advisory: OSV:GHSA-354V-3Q48-CV69...
cadpr (>=0.1.0, <=0.1.1), cfnow (>=0.0.1, <=0.0.6) +19 more potentially affected by CVE-2026-114135 via jupyter-server (>=2.0.1, <=2.5.0)
jupyter-server PYPI version =2.0.1, =0.1.0, =0.0.1, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =3.14.0, =0.3.0, =0.1.2, =0.1.3, =0.0.83, =0.2.13 and more Source cves: CVE-2026-114135 Source advisory: GHSA-354V-3Q48-CV69...
CVE-2026-114135
A flaw was found in jupyter-server. When configured with a gateway connection, the server validates user authentication but fails to verify whether the user has permission to run actions on computational kernels. A remote authenticated user with restricted privileges can exploit this flaw to open...
DEBIAN-CVE-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 WebSocketChannelsHandler, which authenticated the user but did not call authorizer.isauthorized... for the execute action on the kernels...
CVE-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 WebSocketChannelsHandler, which authenticated the user but did not call authorizer.isauthorized... for the execute action on the kernels...
CVE-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 WebSocketChannelsHandler, which authenticated the user but did not call authorizer.isauthorized... for the execute action on the kernels...
UBUNTU-CVE-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 WebSocketChannelsHandler, which authenticated the user but did not call authorizer.isauthorized... for the execute action on the kernels...
CVE-2026-114135 Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization
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.isauthorized... for the execute action on the kernels...