Attack Chain

1. Attacker Crafts Malicious Jupyter Notebook: An authenticated attacker creates a Jupyter notebook containing a specially crafted HTML payload within a display_data output cell, embedding malicious JavaScript.
2. Attacker Uploads/Shares Notebook: The attacker uploads this malicious notebook to a vulnerable jupyter_server instance (versions up to 2.19.0) or shares it with potential victims.
3. Victim Accesses Server: An authenticated victim logs into the jupyter_server instance.
4. Triggering XSS: The victim navigates their browser to the malicious notebook's output view, which is rendered via the /nbconvert/html/<path> endpoint handled by NbconvertFileHandler or NbconvertPostHandler.
5. Vulnerable Rendering: The jupyter_server renders the user-authored HTML content. Due to the missing sandbox directive in the Content-Security-Policy, the malicious HTML is not isolated and executes without restrictions.
6. Client-Side Execution: The embedded malicious JavaScript executes within the victim's browser, operating under the same origin as the jupyter_server.
7. Token Exfiltration: The executing script accesses the victim's authentication tokens (e.g., cookies, session tokens) and exfiltrates them to an attacker-controlled domain.
8. Kernel RCE: Leveraging the victim's authenticated session, the script utilizes full /api/* authority to interact with Jupyter's internal APIs, potentially achieving Remote Code Execution on the Jupyter kernel or the underlying server.

Impact

The successful exploitation of CVE-2026-44727 can lead to severe consequences for affected jupyter_server instances. An authenticated victim's session tokens, including cookies, can be exfiltrated to an attacker-controlled domain, compromising user accounts and sensitive data. Furthermore, the malicious script executing with full /api/* authority can be used to interact with the Jupyter environment, potentially achieving kernel Remote Code Execution (RCE). This allows an attacker to execute arbitrary commands on the server hosting the Jupyter kernel, leading to data theft, system compromise, or further network penetration. The vulnerability impacts any organization or individual using jupyter_server for data analysis, development, or educational purposes, especially in collaborative environments where users might share notebooks.

Recommendation

• Immediately patch jupyter_server to version v2.20.0 or higher to address CVE-2026-44727.
• For deployments where patching is impractical, implement the provided workaround by adding the Content-Security-Policy modification to your jupyter_server_config.py file.
• Deploy the Sigma rules "Detects CVE-2026-44727 Exploitation — Jupyter nbconvert HTML Handler Access" and "Detects CVE-2026-44727 Probing — Suspicious Characters in Jupyter nbconvert Path" to your SIEM for monitoring.
• Ensure webserver logs are collected and ingested into your security monitoring platform to enable detection of these activities.