JupyterLab: Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json)
CVE-2026-102830 · GHSA-3jqq-pw4j-pqcj · published 2026-10-01
- Severity
- Medium
- CVSS score
- 6.8
- Chance of exploitation (EPSS)
- 0.26%
- Fixed in
- 4.6.4
- Exploitation No known exploitation
- Automatable No
- Technical impact Total
- CISA SSVC
The code in the header ran in the JupyterLab page, in the same origin and session as the authenticated user. It could call the Jupyter Server REST API as that user: read and write any file under the server root, start a kernel and run code in it, and open a terminal where terminals are enabled. Nothing had to be clicked; translating one plural string was enough, and that happens during normal use of the interface. What this changes is who has to be trusted. A language pack is a Python package, and installing one is already a privileged act, so an attacker who can get any package installed has server-side code execution regardless of this issue. …
Upgrade jupyterlab to 4.6.4 or later.
JupyterLab v4.6.4 and v4.5.11 contain the patch. The check now has to match the whole header, so a plural rule followed by anything else is rejected and no function is built from it. JupyterLab 3.x reached end of life and receives no patch. Its users should move to a supported 4.x release. Users of applications that depend on JupyterLab, such as Notebook v7+, should update jupyterlab package too.
Use the English locale, which loads no catalogue: jupyter lab --LabApp.default_locale=en or the following traitlet: c.LabApp.default_locale = 'en' Everyone then sees the interface in English, whatever language they had selected. The command prints nothing when every catalogue is sound. A line of output names the pack to remove.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| jupyterlab | PyPI | >= 3.0.0, <= 4.5.10 | 4.5.11 |
| jupyterlab | PyPI | >= 4.6.0, <= 4.6.3 | 4.6.4 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- HighJupyterLab: Cross-site scripting (XSS) in JupyterLab via notebook cells pasted from the system clipboardjupyterlab, jupyterlab, notebook
- HighJupyterLab: Image viewer allows XSS when opening malicious image in new browser tabjupyterlab, jupyterlab
- HighJupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)jupyterlab, jupyterlab
- HighJupyterLab's command linker attributes in HTML enable one-click command execution from untrusted contentjupyterlab, notebook
- HighJupyterLab has an Extension Manager API/GUI Policy Discrepancy, allowing 3rd party (malicious) extensions install via POST requestjupyterlab
- HighJupyter Notebook Vulnerable to Authentication Token Theft via CommandLinker XSSjupyterlab, notebook
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.