Atomicorp WAF Research Note: CVE-2026-44181

Jupyter Enterprise Gateway: Jinja2 Template Server Side Template Injection results in Remote Code Execution

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2026-44181
• Name: Jupyter Enterprise Gateway: Jinja2 Template Server Side Template Injection results in Remote Code Execution
• Severity: Critical
• CVSS: 10.0 (v4.0) (Critical)
• CVSS version: 4.0
• CVSS source: GitHub_M CNA
• CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
  • Attack vector: Network
  • Attack complexity: Low
  • Attack requirements: None
  • Privileges required: None
  • User interaction: None
  • Vulnerable-system confidentiality: High
  • Vulnerable-system integrity: High
  • Vulnerable-system availability: High
  • Subsequent-system confidentiality: High
  • Subsequent-system integrity: High
  • Subsequent-system availability: High
  • Scope: X
• CWE: CWE-1336 — Improper Neutralization of Special Elements Used in a Template Engine
• Vendor: jupyter
• Vulnerable product: enterprise gateway
• CVE published: 2026-07-16
• CVE last modified: 2026-08-05
• Affected versions (NVD configurations):
  • enterprise gateway: >= 2.1.0, < 3.3.0
  • enterprise gateway: 2.0.0
  • enterprise gateway: 2.0.0 rc2
• EPSS: 0.0070; 51.2th percentile (FIRST (opens in a new tab) )
• Latest Update: 2026-09-06
• Selected Rule IDs observed: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
• Matching rules: 10; rules with blocking actions: 10
• Would-block Rule IDs: 340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
• Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data

Vulnerability Description

Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340014 , 340023 , 340029 , 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: jupyter-server enterprise_gateway version >= 2.0.0rc2, < 3.3.0.
   • The CVE record does not include written upgrade or workaround instructions, but it does publish the following patch or mitigation reference:
     • Patch or mitigation information (opens in a new tab)

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• Patch or mitigation: https://github.com/jupyter-server/enterprise_gateway/releases/tag/v3.3.0 (opens in a new tab)
• Vendor advisory: https://github.com/jupyter-server/enterprise_gateway/security/advisories/GHSA-f49j-v924-fx9w (opens in a new tab)

Test or Research Source

• Source: Atomicorp AI Research Framework
• Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .