p PatchFirst

CVE-2026-44182

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 10.0 · Critical · EPSS 0.6% · Fix available

Published
Updated

Stack: python

Affected products and versions

  • enterprise_gateway

    Versions
    • < 3.3.0: Affected

    No fix published

  • jupyter-enterprise-gateway PyPI

    Versions
    • 0.5.0.dev0
    • 0.5.0.dev1
    • 0.5.0.dev2
    • 0.6.0
    • 0.7.0
    • 0.8.0
    • 0.9.0
    • 0.9.1
    • 0.9.2
    • 0.9.3
    • 0.9.4
    • 1.0.0
    • 1.0.1
    • 1.0.2
    • 1.1.0
    • 1.1.1
    • 1.2.0
    • 2.0.0
    • 2.0.0b1
    • 2.0.0rc1
    • 2.0.0rc2
    • 2.1.0
    • 2.1.1
    • 2.2.0
    • 2.2.0rc1
    • 2.2.0rc2
    • 2.3.0
    • 2.4.0
    • 2.5.0
    • 2.5.1
    • 2.5.2
    • 2.6.0
    • 3.0.0
    • 3.0.0b0
    • 3.0.0rc0
    • 3.0.0rc1
    • 3.1.0
    • 3.2.0
    • 3.2.1
    • 3.2.2
    • 3.2.3
    Affected ranges
    • ECOSYSTEM: < 3.3.0

    Update to 3.3.0

Original sources

Check your server →