← Back
CVE-2026-44180
critical
CVSS 9.8
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-180) exists in jupyter_enterprise_gateway. Attackers reach the vulnerable code path via ``KERNEL_UID`` without authentication.
📍 Affected scope
jupyter_enterprise_gateway — . Attack surface: `KERNEL_UID` / `KERNEL_GID` / `prohibited_uids` / `EG_PROHIBITED_UIDS`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.3.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jupyter_enterprise_gateway to 3.3.0ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
jupyter_enterprise_gateway
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.0"}]}]
PyPI
jupyter-enterprise-gateway
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0rc1"},{"fixed":"3.3.0"}]}]
References
- advisory https://github.com/advisories/GHSA-chq7-94j8-cj28
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44180
- package https://github.com/jupyter-server/enterprise_gateway
- package https://pypi.org/project/jupyter-enterprise-gateway
- web https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-chq7-94j8-cj28
- web https://github.com/jupyter-server/enterprise_gateway/releases/tag/v3.3.0