CVE-2026-44180 — Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed…¶

Key facts

CVE-2026-44180 is a Critical (9.8) vulnerability: Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed…. This entry ships a detection-only PoC and a Docker test lab.


CVE	CVE-2026-44180
Severity	Critical (9.8)
Detection / prevention	—
PoC	poc.py
Source	2026/CVE-2026-44180/

Details¶

English | 한국어

Description¶

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.

Vulnerability Details¶

Property	Value
CVE ID	CVE-2026-44180
CVSS Score	9.8

Proof of Concept¶

Download¶

# Download PoC script
curl -O https://raw.githubusercontent.com/fankh/vulnerability-poc/main/2026/CVE-2026-44180/poc.py

Usage¶

# Run PoC against target
python3 poc.py --target <TARGET_URL>

# With authentication
python3 poc.py --target <TARGET_URL> --username <USER> --password <PASS>

⚠️ Warning: This PoC is for authorized security testing only. It uses detection-only techniques and does not exploit or damage target systems.

Test Lab¶

This repository includes a Docker-based test environment with both vulnerable and patched applications.

Quick Start¶

# Clone and navigate to CVE directory
cd CVE-2026-44180

# Start both applications
docker-compose up -d

# Run tests
./run-tests.sh    # Linux/Mac
./run-tests.ps1   # Windows PowerShell

Application Endpoints¶

Application	URL	Status
Vulnerable App	http://localhost:8080	Shows vulnerability
Patched App	http://localhost:8081	Demonstrates fix

Directory Structure¶

├── README.md           # English documentation
├── README_KO.md        # Korean documentation
├── poc.py              # PoC detection script
├── docker-compose.yml  # Container orchestration
├── run-tests.sh        # Linux/Mac test runner
├── run-tests.ps1       # Windows test runner
├── vulnerable-app/     # Vulnerable version
│   ├── app.py
│   ├── Dockerfile
│   └── requirements.txt
└── patched-app/        # Fixed version
    ├── app.py
    ├── Dockerfile
    └── requirements.txt

References¶

https://github.com/jupyter-server/enterprise_gateway/releases/tag/v3.3.0
https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-chq7-94j8-cj28

Generated by PoC Generator on 2026-07-17T09:29:16.584425595

Frequently asked questions¶

What is CVE-2026-44180?¶

CVE-2026-44180 is a Critical (9.8) vulnerability: Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed…. This entry ships a detection-only PoC and a Docker test lab.

How do I detect CVE-2026-44180?¶

Run the detection-only PoC included with this entry against your Docker test lab to confirm whether a target is affected; pair it with your own IDS logging.

How do I block or mitigate CVE-2026-44180?¶

Upgrade to a fixed version per the vendor advisory; the NVD record lists the affected versions. Use the included PoC to verify your remediation.

For authorized security testing and research only. See the full source and NVD record.