Skip to content

CVE-2026-44181

Jupyter Enterprise Gateway vulnerability

10.0 CRITICALPublic exploitEPSS 0.77%
  1. Published16 Jul 2026

Description

Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, 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. This issue has been fixed in version 3.3.0.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Jupyter Enterprise Gateway≥ 2.1.0 < 3.3.0 · 2.0.0

Remediation

Fixed in
Jupyter Enterprise Gateway≥ 3.3.0

Frequently asked

Is CVE-2026-44181 being actively exploited?

CVE-2026-44181 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.77%.

How severe is CVE-2026-44181?

CVE-2026-44181 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.77% probability of exploitation.

Which products are affected by CVE-2026-44181?

Affected products include Jupyter Enterprise Gateway.

How do I fix CVE-2026-44181?

Upgrade affected software to a fixed version, for example Jupyter Enterprise Gateway 3.3.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-44181 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.