CVE-2026-44180
Full vulnerability record from the local CVENow database.
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.
View original CVE JSON
{
"id": "CVE-2026-44180",
"sourceIdentifier": "[email protected]",
"published": "2026-07-16T22:17:02.237",
"lastModified": "2026-10-24T20:10:00.137",
"vulnStatus": "Analyzed",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
},
{
"lang": "es",
"value": "Jupyter Enterprise Gateway lanza kernels remotos de Jupyter Notebook en clústeres distribuidos como Apache Spark, Kubernetes y Docker Swarm. Las versiones 2.0.0rc1 y superiores anteriores a la 3.3.0 tienen una característica de UID y GID prohibidos que, por defecto, impide el lanzamiento de kernels con UID o GID 0 (root), y esta restricción puede ser eludida utilizando un valor KERNEL_UID o KERNEL_GID especialmente diseñado. Esta vulnerabilidad de validación de entrada permite ejecutar kernels de Jupyter como root, lo que puede ser peligroso ya que permite una mayor superficie de ataque, y puede conducir a escapes de contenedor, comprometiendo el nodo trabajador y todas las cargas de trabajo que se ejecutan en él. La explotación repetida puede comprometer todos los nodos trabajadores y, por lo tanto, todo el clúster de Kubernetes. Es posible especificar montajes de volumen, por lo que un vector para un escape de contenedor es usar un montaje de volumen hostPath R/W, usar este bypass de UID/GID para ejecutar como root, y luego obtener ejecución de código en el nodo trabajador subyacente creando una entrada de crontab en el sistema de archivos del host montado. Este problema ha sido solucionado en la versión 3.0.0."
}
],
"affected": [
{
"source": "[email protected]",
"affectedData": [
{
"vendor": "jupyter-server",
"product": "enterprise_gateway",
"versions": [
{
"version": ">= 2.0.0rc1, < 3.3.0",
"status": "affected"
}
]
}
]
}
],
"metrics": {
"cvssMetricV31": [
{
"source": "[email protected]",
"type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "NONE",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"availabilityImpact": "HIGH"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"timestamp": "2026-07-17T14:20:43.912230Z",
"id": "CVE-2026-44180",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
]
},
"weaknesses": [
{
"source": "[email protected]",
"type": "Secondary",
"description": [
{
"lang": "en",
"value": "CWE-20"
}
]
}
],
"configurations": [
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:jupyter:enterprise_gateway:*:*:*:*:*:*:*:*",
"versionStartIncluding": "2.1.0",
"versionEndExcluding": "3.3.0",
"matchCriteriaId": "6708090E-6296-46D7-A202-FA7EA01A1AFF"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:jupyter:enterprise_gateway:2.0.0:-:*:*:*:*:*:*",
"matchCriteriaId": "1E5AAFD0-7061-47AF-95C0-85C431C8B282"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:jupyter:enterprise_gateway:2.0.0:rc1:*:*:*:*:*:*",
"matchCriteriaId": "6A8DDF1A-944D-477D-9C04-E1B2439B0A02"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:jupyter:enterprise_gateway:2.0.0:rc2:*:*:*:*:*:*",
"matchCriteriaId": "1DD83BA8-918B-4A31-B7CB-1868DAF69195"
}
]
}
]
}
],
"references": [
{
"url": "https://github.com/jupyter-server/enterprise_gateway/releases/tag/v3.3.0",
"source": "[email protected]",
"tags": [
"Product",
"Release Notes"
]
},
{
"url": "https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-chq7-94j8-cj28",
"source": "[email protected]",
"tags": [
"Exploit",
"Vendor Advisory"
]
},
{
"url": "https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-chq7-94j8-cj28",
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Vendor Advisory"
]
}
]
}