No immediate action required for standard deployments — default JupyterLab installations using official mathjax/katex extensions are unaffected. Upgrade to JupyterLab 4.4.8 as routine patch hygiene. If your data science teams run custom third-party LaTeX rendering extensions, audit those extensions for target=_blank usage before dismissing.
Risk Assessment
Negligible real-world risk. EPSS of 0.00031 reflects near-zero exploitation probability. The attack is theoretical: it requires a non-existent precondition — a third-party LaTeX extension that adds target=_blank, of which none are known at time of disclosure. The patch is a defense-in-depth improvement enforcing secure link rendering defaults. Not in CISA KEV. Not exploitable in default configurations.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| jupyterlab | pip | <= 4.4.7 | 4.4.8 |
Do you use jupyterlab? You're affected.
Severity & Risk
Recommended Action
5 steps-
Upgrade jupyterlab to 4.4.8 (pip install --upgrade jupyterlab).
-
Audit any non-official LaTeX typesetter extensions in your JupyterLab deployment for target=_blank in link rendering.
-
Enforce extension allowlisting policies — only permit vetted extensions in production data science environments.
-
No workarounds needed for default installations.
-
Detection: review installed JupyterLab extensions (jupyter labextension list) for unrecognized LaTeX rendering plugins.
CISA SSVC Assessment
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2025-59842?
No immediate action required for standard deployments — default JupyterLab installations using official mathjax/katex extensions are unaffected. Upgrade to JupyterLab 4.4.8 as routine patch hygiene. If your data science teams run custom third-party LaTeX rendering extensions, audit those extensions for target=_blank usage before dismissing.
Is CVE-2025-59842 actively exploited?
No confirmed active exploitation of CVE-2025-59842 has been reported, but organizations should still patch proactively.
How to fix CVE-2025-59842?
1. Upgrade jupyterlab to 4.4.8 (pip install --upgrade jupyterlab). 2. Audit any non-official LaTeX typesetter extensions in your JupyterLab deployment for target=_blank in link rendering. 3. Enforce extension allowlisting policies — only permit vetted extensions in production data science environments. 4. No workarounds needed for default installations. 5. Detection: review installed JupyterLab extensions (jupyter labextension list) for unrecognized LaTeX rendering plugins.
What systems are affected by CVE-2025-59842?
This vulnerability affects the following AI/ML architecture patterns: data science workbenches, training pipelines, model development environments.
What is the CVSS score for CVE-2025-59842?
No CVSS score has been assigned yet.
Technical Details
NVD Description
Links generated with LaTeX typesetters in Markdown files and Markdown cells in JupyterLab and Jupyter Notebook did not include the `noopener` attribute. This is deemed to have no impact on the default installations. Theoretically users of third-party LaTeX-rendering extensions could find themselves vulnerable to reverse tabnabbing attacks if: - links generated by those extensions included `target=_blank` (no such extensions are known at time of writing) and - they were to click on a link generated in LaTeX (typically visibly different from other links). For consistency with handling on other links, new versions of JupyterLab will enforce `noopener` and `target=_blank` on all links generated by typesetters. The former will harden the resilience of JupyterLab to extensions with lack of secure defaults in link rendering, and the latter will improve user experience by preventing accidental state loss when clicking on links rendered by LaTeX typesetters. ### Impact Since the official LaTeX typesetter extensions for JupyterLab: `jupyterlab-mathjax` (default), `jupyterlab-mathjax2` and `jupyterlab-katex` do not include the `target=_blank`, there is no impact for JupyterLab users. ### Patches JupyterLab 4.4.8 ### Workarounds No workarounds are necessary. ### References None
Exploitation Scenario
An adversary publishes a malicious JupyterLab LaTeX rendering extension to PyPI or npm that injects target=_blank into rendered links. A data scientist installs it to enable a specific LaTeX rendering feature. When they open a notebook containing LaTeX-rendered hyperlinks and click one, window.opener remains accessible to the destination page. The adversary's server detects the window.opener reference and silently redirects the original JupyterLab tab to a convincing fake login page, harvesting the researcher's credentials — which may include API keys for LLM services, model registries, or cloud ML platforms.
References
Timeline
Related Vulnerabilities
CVE-2025-59528 10.0 Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Supply Chain CVE-2024-2912 10.0 BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Supply Chain CVE-2025-5120 10.0 smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Supply Chain CVE-2023-3765 10.0 MLflow: path traversal allows arbitrary file read
Same attack type: Supply Chain GHSA-vvpj-8cmc-gx39 10.0 picklescan: security flaw enables exploitation
Same attack type: Supply Chain
AI Threat Alert