<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T21:17:01.628931+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-114135</id>
    <title>BREW-jupyterlab-CVE-2026-114135 — Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization</title>
    <updated>2026-11-16T21:17:01.881575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: jupyterlab</p>
<p>### Summary</p>
<p>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.</p>
<p>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.</p>
<p>### Details</p>
<p>The normal handler performs the expected authorization check before creating the WebSocket connection:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/services/kernels/websocket.py#L39-L47</p>
<p>The gateway handler only checks `current_user` and then opens the upstream channel. It never calls `authorizer.is_authorized(...)`:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/gateway/handlers.py#L49-L75
https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/gateway/handlers.py#L87-L98</p>
<p>Gateway mode selected that handler automatically by replacing handlers with matching routes:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/serverapp.py#L437-L446</p>
<p>PR #1261 stopped replacing the normal handler and routed gateway traffic through `GatewayWebSocketConnection` instead. This appears to have fixed the default gateway configuration in 2.6.0, although the deprecated handler is…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-jupyterlab-cve-2026-114135"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-393954</id>
    <title>EUVD-2026-393954</title>
    <updated>2026-11-16T21:17:01.881655+00:00</updated>
    <content>EUVD-2026-393954</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-393954"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-114135</id>
    <title>fkie_cve-2026-114135</title>
    <updated>2026-11-16T21:17:01.881671+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-114135"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-354v-3q48-cv69</id>
    <title>GHSA-354v-3q48-cv69 — Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization</title>
    <updated>2026-11-16T21:17:01.881699+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: jupyter-server</p>
<p>### Summary</p>
<p>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.</p>
<p>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.</p>
<p>### Details</p>
<p>The normal handler performs the expected authorization check before creating the WebSocket connection:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/services/kernels/websocket.py#L39-L47</p>
<p>The gateway handler only checks `current_user` and then opens the upstream channel. It never calls `authorizer.is_authorized(...)`:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/gateway/handlers.py#L49-L75
https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/gateway/handlers.py#L87-L98</p>
<p>Gateway mode selected that handler automatically by replacing handlers with matching routes:</p>
<p>https://github.com/jupyter-server/jupyter_server/blob/v2.5.0/jupyter_server/serverapp.py#L437-L446</p>
<p>PR #1261 stopped replacing the normal handler and routed gateway traffic through `GatewayWebSocketConnection` instead. This appears to have fixed the default gateway configuration in 2.6.0, although the deprecated handler is…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-354v-3q48-cv69"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:95872</id>
    <title>RHSA-2026:95872 — Red Hat Security Advisory: RHOAI 3.5.3 - Red Hat OpenShift AI</title>
    <updated>2026-11-16T21:17:01.881740+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>markdown: python-markdown: Denial of Service via inefficient inline link parsing undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives @fastify/static: @fastify/static: Information disclosure via route guard bypass fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority undici: undici: Denial of Service via unrequested WebSocket subprotocol extract-zip: extract-zip: Arbitrary file write via symlink in archive encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal find-my-way: find-my-way: Denial of Service vulnerability in HTTP/2 server systeminformation: systeminformation: Arbitrary Command Execution via OS Command Injection mlflow: mlflow: Arbitrary file write via FileStore path traversal mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers nltk: NLTK: Information Disclosure via Symlink Sandbox Bypass github.com/klauspost/compress: klauspost/compress: Denial of Service via integer overflow in dictionary processing com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via excessively long JSON property names accelerate: Hugging Face Accelerate: Path Traversal and Denial of Service via weight_map brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation aiohttp: AIOHTTP: HTTP Request Smuggling via WebSocket Upgrade aiohttp: AIOHTTP: Denial of Ser…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:95872"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114135</id>
    <title>UBUNTU-CVE-2026-114135</title>
    <updated>2026-11-16T21:17:01.882058+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: jupyter-server, Ubuntu:24.04:LTS: jupyter-server, Ubuntu:26.10: jupyter-server, Ubuntu:26.04:LTS: jupyter-server</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-114135"/>
  </entry>
</feed>
