Lucene search
+L

4 matches found

Github Security Blog
Github Security Blog
•added 2026/10/22 3:46 p.m.•2 views

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...

8.8CVSS5.9AI score0.00386EPSS
SaveExploits0References6Affected Software1
osv_ghsa
osv_ghsa
•added 2026/10/22 3:46 p.m.•1 views

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...

8.8CVSS5.9AI score0.00386EPSS
SaveExploits0References6
CVE
CVE
•added 2026/10/21 7:58 p.m.•21 views

CVE-2026-114135

Jupyter Server (versions 2.0.0 through 2.6.0) is vulnerable to an authorization bypass when GatewayClient.url is enabled. The WebSocketChannelsHandler fails to call authorizer.is_authorized(...) for the execute action on the kernels resource, allowing a restricted authenticated user to open an up...

8.8CVSS6.1AI score0.00386EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/21 7:58 p.m.•20 views

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...

8.8CVSS0.00386EPSS
SaveExploits0References4
Rows per page
Query Builder