Exploit discussion active in current signal (1 latest mentions)
Recommended action window: High priority (within 72h)
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
1 version affected across 1 product
| Date | Total | Labels |
|---|
| 2026-06-11 | 1 | Disclosure1 |
| 2026-07-17 | 2 | Disclosure2 |
| 2026-08-11 | 1 | General1 |
CVE-2026-44182, CVE-2026-44181, CVE-2026-44180 Critical Jupyter Enterprise Gateway Vulnerabilities Enable Full Kubernetes Cluster Takeover https://orca.security/resources/blog/jupyter-enterprise-gateway-vulnerabilities/
Post summary
The post announces critical CVEs against Jupyter Enterprise Gateway that could enable full Kubernetes cluster takeover, but provides no technical or exploitation details.
Jupyter Enterprise Gatewayに重大脆弱性3件、Kubernetesクラスタ侵害のおそれ https://www.cybernote.click/2026/08/09/jupyter-enterprise-gateway-cve-2026-44180-44181-44182/ #IT #Security #cybersecurity
Post summary
The tweet alerts that Jupyter Enterprise Gateway has three critical vulnerabilities (CVE‑2026‑44180, CVE‑2026‑44181, CVE‑2026‑44182) and could lead to Kubernetes cluster compromise, but provides no further technical or mitigation details.
#CVE-2026-44180 - Critical code execution in #Jupyter Enterprise Gateway. Root privilege escalation via crafted KERNEL_UID/GID bypass. #CVSS 9.8. No patch available yet. Mitigate now. #CVEAlert #infosec #devsecops #devops #deveoper #git #gitlab #github https://www.valtersit.com/cve/CVE-2026-44180
Post summary
The tweet announces CVE-2026-44180, a critical root privilege escalation flaw in Jupyter Enterprise Gateway, noting no patch yet and urging mitigation, with a link to more details.
CVE-2026-44180 Input Validation Bypass in Jupyter Enterprise Gateway Allows Root Kernel... https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-44180 Vulnerability Notification: https://alerts.vulmon.com/?utm_source=twitter&utm_medium=social&utm_campaign=2102281&utm_content=3
Post summary
A brief notification of CVE‑2026‑44180 is presented with minimal technical detail, without claims of exploitation, PoC, or remediation.
4 of 4 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | jupyter | enterprise_gateway | - | - | - |
| App | jupyter | enterprise_gateway | 2.0.0 | - | - |
| App | jupyter | enterprise_gateway | 2.0.0 | - | - |
| App | jupyter | enterprise_gateway | 2.0.0 | - | - |