CVE-2026-44180 IBM QRadar · QRadar

Detect CVE-2026-44180: Jupyter Enterprise Gateway ContainerProcessProxy._enforce_prohibited_ids Bypass in IBM QRadar

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

QRadar Detection Query

IBM QRadar (QRadar)
sql
SELECT DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') as event_time, sourceip, destinationip, destinationport, username, "Process Name", "Command"
FROM events
WHERE LOGSOURCETYPENAME(logsourceid) IN ('Linux OS', 'Microsoft Windows Security Event Log', 'UNIX')
  AND ("Command" ILIKE '%enterprise_gateway%' OR "Command" ILIKE '%ContainerProcessProxy%' OR "Process Name" ILIKE '%jupyter%')
  AND ("Command" ILIKE '%kernel_id%' OR "Command" ILIKE '%prohibited_ids%' OR "Command" ILIKE '%enforce_prohibited%')
LAST 24 HOURS
critical severity medium confidence

QRadar AQL query to identify Jupyter Enterprise Gateway command-line patterns associated with CVE-2026-44180 kernel ID bypass attempts.

Data Sources

Linux OSMicrosoft Windows Security Event LogUNIX

Required Tables

events

False Positives & Tuning

  • Automated notebook execution pipelines using kernel IDs for session management
  • Log noise from verbose enterprise gateway debug logging
  • Legitimate multi-user environments where many kernels are spawned concurrently

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