CVE-2026-44182: Jupyter Enterprise Gateway Has Kubernetes Manifest Injection via Jinja2 Template Rendering

Severity: critical (CVSS 10.0 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.6% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-07-16 · updated 2026-10-24
Weakness: CWE-74

Description

Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.

Affected products

jupyter-server enterprise_gateway: before 3.3.0 — fixed in 3.3.0

How to fix

Upgrade to a fixed version: jupyter-server enterprise_gateway 3.3.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-44182 or the next vulnerability affects your stack