---
title: "CVE-2026-44180: Jupyter Enterprise Gateway: ContainerProcessProxy._enforce_prohibited_ids Bypass"
url: https://erroneo.us/security/cve/CVE-2026-44180/
description: "CVE-2026-44180 (jupyter_enterprise_gateway (PyPI)): Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-07-16
date_modified: 2026-07-17
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-44180"
kev: false
cvss: 9.8
epss: 0.00715
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-44180: Jupyter Enterprise Gateway: ContainerProcessProxy._enforce_prohibited_ids Bypass

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.7% , percentile 53: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 53% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes jupyter_enterprise_gateway (PyPI) >= 2.0.0rc1, < 3.3.0, fixed in 3.3.0 . Check your lockfile, including transitive dependencies.

## What it is

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 KERNELUID or KERNELGID 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.

## Affected packages

- PyPI `jupyter_enterprise_gateway` >= 2.0.0rc1, < 3.3.0 → fixed: 3.3.0

## Affected products (CVE record)

- jupyter-server enterprise_gateway: >= 2.0.0rc1, < 3.3.0

## Severity

- GitHub_M CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.71% probability of exploitation activity in the next 30 days; percentile 53.

## Sources

- [GitHub Advisory GHSA-chq7-94j8-cj28](https://github.com/advisories/GHSA-chq7-94j8-cj28)
- [CVE.org record CVE-2026-44180](https://www.cve.org/CVERecord?id=CVE-2026-44180)
- [NVD entry CVE-2026-44180](https://nvd.nist.gov/vuln/detail/CVE-2026-44180)
- [github.com](https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-chq7-94j8-cj28)
- [github.com](https://github.com/jupyter-server/enterprise_gateway/releases/tag/v3.3.0)

---
Source page: https://erroneo.us/security/cve/CVE-2026-44180/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt