GPU VulnDB

Database/AI/ML frameworks & serving

Jupyter Enterprise Gateway: YAML injection in kernel env vars creates arbitrary Kubernetes resources

CVSS 10.0CVE-2026-44182AI/ML frameworks & servingcurated

Impact

Untrusted kernel environment variables (kernel_working_dir and the other kernel_xxx values used by the manifest template) are interpolated into the Kubernetes manifest without YAML-aware escaping. An attacker can add or overwrite fields - duplicate securityContext keys where the last wins - and inject document separators to emit extra resources entirely, including a privileged pod. The result is arbitrary workload creation with the gateway's service account rights, which on a GPU cluster means a privileged container on a GPU node and a path to the host and to other tenants' work. This is a distinct flaw from the Jinja2 template injection in CVE-2026-44181, though the same release fixes both.

Who can reach it

Anyone who can submit a kernel start request to the Enterprise Gateway endpoint and control KERNEL_* values; per the advisory and CVSS vector, no authentication is required.

What to do

Upgrade to Enterprise Gateway 3.3.0 and restart the gateway daemon - no GPU node drain or reboot required. Before the upgrade lands, limit who can reach the gateway and review recently created pods for unexpected privileged or hostPath specs.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.