critical CVSS 9.8

CVE-2026-44180·Docker vulnerability

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
critical
Software
Docker
Fixed in
3.3.0
Published
2026-07-16

Affected versions

From: 2.1.0

Until: 3.3.0

Fixed in: 3.3.0

How to fix this CVE

Upgrade Docker to version 3.3.0 or later to patch the UID/GID bypass vulnerability in Jupyter Enterprise Gateway. This vulnerability allows attackers to launch kernel containers with root privileges, potentially leading to container escapes and cluster compromise. Immediate patching is critical for any environment running Kubernetes or Docker Swarm with Jupyter Enterprise Gateway.

sudo dnf update docker-ce --setopt=allow_downgrade -y

Defensia detects this vulnerability

How to check if you are affected

  1. Check Docker version: docker --version or docker version --format '{{.Server.Version}}'
  2. Identify Jupyter Enterprise Gateway installations: grep -r 'enterprise_gateway' /opt /home /root or ps aux | grep enterprise_gateway
  3. Review kernel launch logs for suspicious UID/GID values: grep -i 'KERNEL_UID\|KERNEL_GID' /var/log/containers/* or journalctl -u docker -S '1 hour ago' | grep -i kernel
  4. Verify patched version is running: docker inspect <container_id> | grep -i 'Image\|RepoTag' and confirm version >= 3.3.0

FAQ

What is CVE-2026-44180?

This is a critical input validation flaw in Jupyter Enterprise Gateway that allows attackers to bypass UID/GID restrictions and launch kernel containers with root privileges, enabling container escapes and compromising entire Kubernetes clusters.

Is CVE-2026-44180 being actively exploited?

No, this vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities catalog and no public exploits are available, but the critical CVSS score and ease of exploitation warrant immediate patching.

What versions of Docker are affected by CVE-2026-44180?

Jupyter Enterprise Gateway versions 2.1.0 through 3.3.0 (specifically 2.0.0rc1 and later prior to 3.3.0) are vulnerable. The vulnerability is patched in version 3.3.0 and later.

How do I check if my server is vulnerable to CVE-2026-44180?

Run: docker inspect <container_id> | grep -A 5 'Image' to identify Jupyter Enterprise Gateway containers, then check the image tag or run: docker exec <container_id> pip show jupyter-enterprise-gateway to confirm the installed version is below 3.3.0.

Does Defensia detect CVE-2026-44180?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker or Jupyter Enterprise Gateway is installed on a monitored server, CVE-2026-44180 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-44180. Free for 1 server.

Get started free