UTC
Medium

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
What it is

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. …

What to do

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.

If you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
jupyterlabPyPI>= 3.0.0, <= 4.5.104.5.11
jupyterlabPyPI>= 4.6.0, <= 4.6.34.6.4

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].