UBUNTU-CVE-2026-114135 (CVE-2026-114135)
Vulnerability from osv_ubuntu – Published: 2026-10-21 20:17 – Updated: 2026-10-28 17:50 – Source websiteJupyter 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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jupyter-server",
"binary_version": "1.13.1-1"
},
{
"binary_name": "python3-jupyter-server",
"binary_version": "1.13.1-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "jupyter-server",
"purl": "pkg:deb/ubuntu/jupyter-server@1.13.1-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.2-1",
"1.13.1-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jupyter-server",
"binary_version": "1.23.3-2"
},
{
"binary_name": "python3-jupyter-server",
"binary_version": "1.23.3-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "jupyter-server",
"purl": "pkg:deb/ubuntu/jupyter-server@1.23.3-2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.23.3-1",
"1.23.3-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jupyter-server",
"binary_version": "2.20.0-3"
},
{
"binary_name": "python3-jupyter-server",
"binary_version": "2.20.0-3"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "jupyter-server",
"purl": "pkg:deb/ubuntu/jupyter-server@2.20.0-3?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.17.0-1",
"2.20.0-3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jupyter-server",
"binary_version": "2.17.0-1"
},
{
"binary_name": "python3-jupyter-server",
"binary_version": "2.17.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "jupyter-server",
"purl": "pkg:deb/ubuntu/jupyter-server@2.17.0-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.15.0-1",
"2.17.0-1"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2026-114135",
"modified": "2026-10-28T17:50:37Z",
"published": "2026-10-21T20:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-114135"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114135"
},
{
"type": "REPORT",
"url": "https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-354v-3q48-cv69"
},
{
"type": "REPORT",
"url": "https://github.com/jupyter-server/jupyter_server/pull/1261"
},
{
"type": "REPORT",
"url": "https://github.com/jupyter-server/jupyter_server/commit/35ffe5d435682128da16dc144a8e9e9f8fa85dd8"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-114135"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.