CVE-2026-102830: JupyterLab: Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json)

Published Sep 29, 2026
·
Updated

JupyterLab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From JupyterLab 3.0.0 until 4.5.11 and 4.6.4, and in JupyterLite Core 0.8.3 and earlier, the Plural-Forms header in a selected third-party language pack can append JavaScript after a valid plural rule because prefix-only regular-expression validation accepts a matching prefix without requiring the entire header to match. JupyterLab passes the accepted expression to new Function, so loading the catalogue and translating a plural string executes the appended code in the authenticated JupyterLab origin. Where Jupyter Server kernels, terminals, and APIs are exposed, the code can use authenticated server APIs to read or modify files and run code. Impact is much more limited in JupyterLite because it typically lacks most exposed Jupyter Server surfaces. The default English locale is unaffected because it does not load a translation catalogue. This issue is fixed in JupyterLab 4.5.11 and 4.6.4 and JupyterLite Core 0.8.4.

Affected Software

2 affected components
jupyter JupyterLab>=3.0.0<4.5.11, >=4.6.0<4.6.4
jupyter JupyterLite Core<=0.8.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.5.11
  2. Upgrade

    Upgrade JupyterLab to a version that resolves this vulnerability.

    Fixed in 4.6.4
  3. Upgrade

    Upgrade JupyterLite Core to a version that resolves this vulnerability.

    Fixed in 0.8.4

Event History

Sep 29, 2026
CVE Published
via MITRE·06:53 PM
Data Sourced
via MITRE·06:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments have the greatest potential impact?

JupyterLab deployments where Jupyter Server kernels, terminals, or APIs are exposed have the greatest impact. Code executed through the issue runs in the authenticated JupyterLab origin and can use those authenticated server APIs to read or modify files and run code.

2

What conditions are needed for exploitation?

A crafted third-party language pack must be selected, its catalogue must be loaded, and a plural string must be translated. The malicious code is appended after an otherwise valid Plural-Forms rule.

3

Are default installations affected?

The default English locale is unaffected because it does not load a translation catalogue. Exposure depends on selecting a third-party language pack.

4

What can be done before an update is available?

Use the default English locale and avoid selecting third-party language packs, particularly untrusted ones. This prevents the affected translation catalogue path from being used.

5

Which releases contain the fix?

The issue is fixed in JupyterLab 4.5.11 and 4.6.4, and in JupyterLite Core 0.8.4.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203