CVE-2026-44181
SSTI in Jupyter Enterprise Gateway enables RCE and full Kubernetes cluster compromise.
Is CVE-2026-44181 being exploited?
Not confirmed. CVE-2026-44181 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.70% probability of exploitation in the next 30 days.
How severe is CVE-2026-44181?
CVE-2026-44181 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-44181?
Yes. A fix has been recorded for CVE-2026-44181. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44181 affect?
CVE-2026-44181 affects Jupyter Enterprise Gateway >=2.0.0rc2 and <3.3.0, Kubernetes clusters (service accounts, secrets), Kernels on Apache Spark, Kubernetes, Docker Swarm. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44181?
Upgrade to Enterprise Gateway 3.3.0; rotate K8s service account tokens and audit/isolate clusters.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-side template injection allows remote code execution, theft of K8s service tokens/secrets, and full cluster takeover (privileged pods/hostPath).
Immediate action required
- affected>= 2.0.0rc2 and < 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.