CVE Watchtower

CVE-2026-44180Jupyter Enterprise Gateway Improper Input Validation

NVDCVSS scored by security-advisories@github.com

Vulnerability Summary

Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. Versions 2.0.0rc1 and above prior to 3.3.0 have a prohibited UID and GID feature that by default prevents launching kernels with UID or GID 0 (root), and this restriction can be bypassed using a specially crafted KERNEL_UID or KERNEL_GID value. This input validation vulnerability allows running Jupyter kernels as root, which can be dangerous as it allows more attack surface, and may lead to container escapes, compromising the worker node and all workloads running on it. Repeated exploitation can compromise all worker nodes, and thus the entire Kubernetes cluster. It is possible to specify volume mounts, so one vector for a container escape is to use a hostPath R/W volume mount, use this UID/GID bypass to run as root, and then gain code execution in the underlying worker node by creating a crontab entry in the mounted host file system. This issue has been fixed in version 3.0.0.
Severity Level
CRITICAL(9.8)
Published Date
Jul 16, 2026
Last Modified
Oct 24, 2026
Exploitation Status
Public exploit available
EPSS Score (30-Day)
0.72%Probability
Root Weakness (CWE)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required.
CVSS v3.1 Base Metrics — Score 9.8 (CRITICAL)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Jupyter Enterprise Gateway >= 2.1.0 and < 3.3.0
  • Jupyter Enterprise Gateway
Patched Versions
  • Jupyter Enterprise Gateway 3.3.0

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run Jupyter Enterprise Gateway and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • Jul 16, 2026Published
  • Oct 24, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Jupyter Enterprise Gateway CVEsYou are reading CVE-2026-44180. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Jupyter Enterprise Gateway CVEs

Data last checked: Nov 18, 2026 23:14 UTC