Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44181 critical CVSS 10.0

Vulnerability in jupyter_enterprise_gateway (CVE-2026-44181)

Summary

Vulnerability in jupyter_enterprise_gateway (CVE-2026-44181). Successful exploitation can lead to full system takeover. Exploitable via KERNEL_XXX. Mitigation: upgrade to 3.3.0 or later.

Original description

The description as published by the source.

Summary

The environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI).
By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service.
The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount.

Details

The KERNEL_POD_NAME variable is rendered using Jinja2, allowing for code execution via template expression statements, in this code:
https://github.com/jupyter-server/enterprise_gateway/blob/152c20f162f2fab700c04c8830ebf8c1e2e2217a/enterprise_gateway/services/processproxies/k8s.py#L219-L247

The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, in addition to kernel_pod_name discussed above, such as kernel_working_dir that are used when rendering the manifest and are all vectors for SSTI.
https://github.com/jupyter-server/enterprise_gateway/blob/152c20f162f2fab700c04c8830ebf8c1e2e2217a/etc/kernel-launchers/kubernetes/scripts/kernel-pod.yaml.j2#L77

These values come from the environment passed in the API call, where they were KERNEL_XXX before being converted to lowercase.

https://github.com/jupyter-server/enterprise_gateway/blob/152c20f162f2fab700c04c8830ebf8c1e2e2217a/etc/kernel-launchers/kubernetes/scr…

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-44181 has been found in jupyter_enterprise_gateway.
Attackers can target a specific entry point like KERNEL_XXX over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/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-44181" on the vendor's site.

CVE-2026-44181 (jupyter_enterprise_gateway) — CWE-1336 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: KERNEL_XXX / hostPath / KERNEL_POD_NAME / kernel_xxx
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-1336) exists in jupyter_enterprise_gateway. Attackers reach the vulnerable code path via KERNEL_XXX without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of jupyter_enterprise_gateway. Attack surface: KERNEL_XXX / hostPath / KERNEL_POD_NAME / kernel_xxx.

🔥 Severity

Severity: Critical (CVSS 10.0/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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'jupyter_enterprise_gateway' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyter_enterprise_gateway を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade jupyter_enterprise_gateway to 3.3.0

    ステージング環境で 3.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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.0rc2"},{"fixed":"3.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details