CVE-2026-44182

Critical

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.

SeverityCritical
CVSS10.0
Exploit probability—
ProductJupyter Enterprise Gateway
PublishedJul 16, 2026
First seenJul 16, 2026
Weakness typeCWE-74Injection

How to fix

Update
  • jupyter enterprise_gateway3.3.0 or later
  • jupyter-enterprise-gateway3.3.0 or later

Affected products

ProductAffected versionsFixed in
jupyter enterprise_gatewayv < 3.3.03.3.0
jupyter-enterprise-gatewayPyPIv < 3.3.03.3.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.