CVE-2026-44180
published 2026-07-16CVE-2026-44180: Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. Versions…
PriorityP263critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.71%
51.9th percentile
Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. Versions 2.0.0rc1 and above prior to 3.3.0 have a prohibited UID and GID feature that by default prevents launching kernels with UID or GID 0 (root), and this restriction can be bypassed using a specially crafted KERNEL_UID or KERNEL_GID value. This input validation vulnerability allows running Jupyter kernels as root, which can be dangerous as it allows more attack surface, and may lead to container escapes, compromising the worker node and all workloads running on it. Repeated exploitation can compromise all worker nodes, and thus the entire Kubernetes cluster. It is possible to specify volume mounts, so one vector for a container escape is to use a hostPath R/W volume mount, use this UID/GID bypass to run as root, and then gain code execution in the underlying worker node by creating a crontab entry in the mounted host file system. This issue has been fixed in version 3.0.0.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| jupyter-server | enterprise_gateway | — | — |
| jupyter | enterprise_gateway | — | — |
| jupyter | enterprise_gateway | — | — |
| jupyter | enterprise_gateway | — | — |
| jupyter | enterprise_gateway | >= 2.1.0 < 3.3.0 | 3.3.0 |
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.
VulDB
jupyter-server enterprise_gateway up to 3.2.x Kernel Launch KERNEL_UID/KERNEL_GID input validation
vuldb·2026-07-17·CVSS 9.8
CVE-2026-44180 [CRITICAL] jupyter-server enterprise_gateway up to 3.2.x Kernel Launch KERNEL_UID/KERNEL_GID input validation
A vulnerability classified as critical was found in jupyter-server enterprise_gateway up to 3.2.x. Affected by this issue is some unknown functionality of the component Kernel Launch. Executing a manipulation of the argument KERNEL_UID/KERNEL_GID can lead to improper input validation.
This vulnerability is handled as CVE-2026-44180. The attack can be executed remotely. There is not any exploit available.
GHSA
Jupyter Enterprise Gateway: ContainerProcessProxy._enforce_prohibited_ids Bypass
ghsa·2026-06-03
CVE-2026-44180 [CRITICAL] CWE-180 Jupyter Enterprise Gateway: ContainerProcessProxy._enforce_prohibited_ids Bypass
Jupyter Enterprise Gateway: ContainerProcessProxy._enforce_prohibited_ids Bypass
### Summary
Jupyter Enterprise Gateway has a prohibited UID and GID feature that by default prevents launching kernels with UID or GID 0 (root).
This can be bypassed. It is possible to launch kernels with a prohibited UID and/or GID by using a specially crafted `KERNEL_UID` or `KERNEL_GID` value.
The feature is described in the documentation:
https://github.com/jupyter-server/enterprise_gateway/blob/152c20f162f2fab700c04c8830ebf8c1e2e2217a/docs/source/operators/config-add-env.md?plain=1#L103-L107
https://github.com/jupyter-server/enterprise_gateway/blob/152c20f162f2fab700c04c8830ebf8c1e2e2217a/docs/source/operators/config-add-env.md?plain=1#L88-L92
https://github.com/jupyter-server/enterprise_gateway/blo
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-07-16
Published