CVE-2026-44182
YAML injection in Jupyter Enterprise Gateway enables creation of privileged Kubernetes resources.
Is CVE-2026-44182 being exploited?
Not confirmed. CVE-2026-44182 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-44182?
CVE-2026-44182 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44182?
Yes. A fix has been recorded for CVE-2026-44182. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44182 affect?
CVE-2026-44182 affects Jupyter Enterprise Gateway <3.3.0, Kubernetes clusters using JEG, Apache Spark/Kubernetes/Docker Swarm kernel launches. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44182?
Upgrade to Jupyter Enterprise Gateway >=3.3.0; sanitize env vars and restrict pod/SA privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Untrusted env vars in templates allow YAML injection to create/modify Kubernetes resources (e.g., privileged pods), enabling privilege escalation and cluster compromise.
Immediate action required
- affected< 3.3.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.