CVE-2026-44180 Google Chronicle · YARA-L

Detect CVE-2026-44180: Jupyter Enterprise Gateway ContainerProcessProxy._enforce_prohibited_ids Bypass in Google Chronicle

CVE-2026-44180 is a critical (CVSS 9.8) input validation bypass in Jupyter Enterprise Gateway versions >= 2.0.0rc1 and < 3.3.0. The ContainerProcessProxy._enforce_prohibited_ids method fails to properly validate or enforce restrictions on kernel IDs, allowing an attacker to bypass container process isolation controls. This can enable unauthorized kernel spawning, container escape, or execution of arbitrary workloads within the enterprise gateway environment. A public proof-of-concept exists.

MITRE ATT&CK

Tactic
Initial Access Privilege Escalation Lateral Movement

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_44180_jupyter_gateway_bypass {
  meta:
    author = "df00tech"
    description = "Detects CVE-2026-44180 Jupyter Enterprise Gateway ContainerProcessProxy prohibited ID bypass"
    severity = "CRITICAL"
    priority = "HIGH"
  events:
    $e.metadata.event_type = "PROCESS_LAUNCH"
    $e.principal.process.file.full_path = /python/ nocase
    (
      $e.principal.process.command_line = /enterprise_gateway/ nocase or
      $e.principal.process.command_line = /ContainerProcessProxy/ nocase or
      $e.principal.process.command_line = /kernel[_\-]id=[a-zA-Z0-9_\-]{8,}/ nocase
    )
  condition:
    $e
}
critical severity medium confidence

Chronicle YARA-L rule to detect Jupyter Enterprise Gateway process launches with kernel ID manipulation patterns indicative of CVE-2026-44180 exploitation.

Data Sources

EDR process telemetryChronicle UDM

Required Tables

UDM Events

False Positives & Tuning

  • Legitimate gateway administration scripts with explicit kernel ID parameters
  • Automated test runners in CI environments targeting gateway endpoints
  • Monitoring agents that enumerate active kernels via gateway API

Other platforms for CVE-2026-44180


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Spawn unauthorized kernel via ID bypass on vulnerable gateway

    Expected signal: Process creation events for python3 spawned as child of jupyter-enterprise-gateway with command line containing the test kernel_id value; HTTP access log entries showing POST /api/kernels with status 201 for requests that should have been rejected

  2. Test 2Enumerate gateway kernel API for ID restriction bypass

    Expected signal: Multiple sequential HTTP POST requests to /api/kernels gateway endpoint within a short timeframe with varying kernel_id values including path traversal and command injection patterns

  3. Test 3Simulate container escape via unrestricted kernel process spawning

    Expected signal: Container process creation events showing python3 kernel process; if escape is successful, process events outside container namespace; file access events for /proc/1/cgroup or /etc/hosts from kernel process

Unlock Pro Content

Get the full detection package for CVE-2026-44180 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections