critical CVSS 10

CVE-2026-44182·Docker vulnerability

Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.

Severity
critical
Software
Docker
Fixed in
3.3.0
Published
2026-07-16

Affected versions

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 YAML injection vulnerability in Jupyter Enterprise Gateway that allows attackers to manipulate Kubernetes manifests. This critical flaw enables privilege escalation through arbitrary pod creation when Docker is used with distributed cluster orchestration. Apply the update immediately across all affected systems, then validate the deployment to ensure kernel isolation remains intact.

sudo dnf update docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Run `docker --version` to check the installed Docker version and confirm it is version 3.3.0 or later
  2. Verify if Jupyter Enterprise Gateway is installed by running `pip list | grep jupyter-enterprise-gateway` or checking the running containers with `docker ps --filter 'ancestor=jupyter/enterprise-gateway'`
  3. Search Docker container logs for YAML injection attempts by examining manifests: `docker logs <container_id> | grep -i 'kernel_' | grep -E '(---|\.\.\.|securityContext)'`
  4. Confirm the patch by checking the Jupyter Enterprise Gateway version with `pip show jupyter-enterprise-gateway` or inspecting the container image: `docker inspect <image_id> | grep -i version`

FAQ

What is CVE-2026-44182?

This is a critical YAML injection vulnerability in Jupyter Enterprise Gateway that allows unauthenticated attackers to manipulate Kubernetes manifest files by injecting malicious content through unsanitized environment variables. An attacker can exploit this to create privileged container pods, leading to complete system compromise.

Is CVE-2026-44182 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the critical CVSS score of 10.0 means organizations should prioritize remediation immediately.

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

All versions of Docker using Jupyter Enterprise Gateway prior to version 3.3.0 are vulnerable. This includes any deployment combining Docker Swarm, Kubernetes, or Apache Spark with unpatched Enterprise Gateway components.

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

Run `pip show jupyter-enterprise-gateway | grep Version` to check the installed version. If the version is below 3.3.0, the system is vulnerable. Additionally, check running containers with `docker ps --format '{{.ID}}\t{{.Image}}'` and inspect any Enterprise Gateway images for version tags.

Does Defensia detect CVE-2026-44182?

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

Related Docker CVEs

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.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
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-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-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.

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-44182. Free for 1 server.

Get started free