Vulnerability in jupyter_enterprise_gateway (CVE-2026-44180)
Summary
Vulnerability in jupyter_enterprise_gateway (CVE-2026-44180). Successful exploitation can lead to full system takeover. Exploitable via KERNEL_UID. Mitigation: upgrade to 3.3.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44180 has been found in jupyter_enterprise_gateway.
Attackers can target a specific entry point like KERNEL_UID over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade jupyter_enterprise_gateway to 3.3.0 or later.
If unsure, ask your IT team or search "jupyter_enterprise_gateway CVE-2026-44180" on the vendor's site.
CVE-2026-44180 (jupyter_enterprise_gateway) — CWE-180 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: KERNEL_UID / KERNEL_GID / prohibited_uids / EG_PROHIBITED_UIDS
Patched: 3.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-180) exists in jupyter_enterprise_gateway. Attackers reach the vulnerable code path via KERNEL_UID without authentication.
Check the vendor advisory for the affected versions of jupyter_enterprise_gateway. Attack surface: KERNEL_UID / KERNEL_GID / prohibited_uids / EG_PROHIBITED_UIDS.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jupyter_enterprise_gateway' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jupyter_enterprise_gateway' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jupyter_enterprise_gatewayを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jupyter_enterprise_gateway to 3.3.0ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com