Vulnary
← back to the feed
Critical· 10official fix available

CVE-2026-44181

Jupyter Enterprise Gateway versions 2.0.0rc2 through 3.2.x are vulnerable to server‑side template injection in the Kubernetes manifest rendering process. An attacker can inject Jinja2 expressions to execute arbitrary Python code and OS commands, potentially stealing the Kubernetes service account token and fully compromising the cluster. The issue is resolved in version 3.3.0.

publishedJul 17, 2026
last modifiedJul 17, 2026
sourcesNVD
severity · cvss
10
critical · how bad it is
exploitation · epss
<1%
38th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 18, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Jupyter Enterprise Gateway

02

Real-world impact

Full Kubernetes cluster compromise via privileged pod or hostPath volume mount.

03

Why this severity

CVSS 4.0 base score 10 (critical) due to network‑adjacent, low‑complexity attack with high impacts on confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 011. Upgrade Jupyter Enterprise Gateway to version 3.3.0 or later.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 17, 2026 · 17d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 19, 2026 · 15d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
CVE-2026-44181: Jupyter Enterprise Gateway versions 2.0.0rc2 through 3.2.x are vulnera · Vulnary