CVE-2026-102830: JupyterLab Cross-Site Scripting Vulnerability

MODERATE
Advisory Identifier: GHSA-3jqq-pw4j-pqcj
CVSS 6.8
CWE-94 CWE-79 CWE-625
Published
Advisory Summary

CVE-2026-102830 is a MODERATE (CVSS 6.8) cross-site scripting vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting JupyterLab libraries in the PyPI ecosystem. The issue involves cross-site scripting (xss) in jupyterlab via crafted language package (jupyterlab.json). Remediation is available by upgrading affected packages to version 4.6.4, 4.5.11, 0.8.4.

CVE-2026-102830 at a Glance

CVE Identifier CVE-2026-102830
GHSA Identifier GHSA-3jqq-pw4j-pqcj
Severity MODERATE
CVSS v3.1 Base Score 6.8
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product JupyterLab
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-102830

To remediate this vulnerability, upgrade all affected JupyterLab dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

jupyterlab fixed: 4.6.4
pip install jupyterlab>=4.6.4
jupyterlab fixed: 4.5.11
pip install jupyterlab>=4.5.11
jupyterlite-core fixed: 0.8.4
pip install jupyterlite-core>=0.8.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show jupyterlab

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-102830, inspect your installed packages using pip:

pip show jupyterlab

Analyze the terminal output to locate any version of JupyterLab in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.6.4), your application is affected.

Note: The pip show jupyterlab command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In JupyterLab, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Description A language pack ships a `Plural-Forms` header saying how the language counts, for example `nplurals=2; plural=(n != 1);`. JupyterLab turns that string into a function with `new Function`, so the header gets executed. The check that meant to keep it safe was a regular expression. The regex was anchored at the start but not at the end, so it accepted any string that began with a valid plural rule and ignored everything after it. A header such as the following passed the check, and the part after the plural rule ran in the JupyterLab page as soon as the first plural string was translated: ``` nplurals=2; plural=(n > 1); <anything here ran as JavaScript> ``` Users are affected if all of the following are true: - they run JupyterLab 3.0.0 through 4.6.3, or an application that bundles it such as Notebook 7; - a language pack they did not write is installed in the environment; and - that language is selected, so its catalogue is loaded An installation using the default English locale loads no catalogue and is not affected. > CVE assignment pending, GitHub CNA is experiencing severe backlog ### Impact 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. The header is different because it is catalogue metadata: it travels with translation content, through the [translation pipeline](https://jupyterlab.readthedocs.io/en/latest/developer/internationalization.html) that carries strings from Crowdin into the language packs, and it is reviewed as text rather than as code. Anyone able to change a catalogue, or to publish a pack under a name someone installs, got JavaScript execution in every browser that selected that language. Note: the impact is much more limited on JupyterLite which typically does not have access to most of the surfaces that this flaw exposes. ### Patches JupyterLab [`v4.6.4`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4) and [`v4.5.11`](https://github.com/jupyterlab/jupyterlab/releases/tag/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. ### Workarounds Use the English locale, which loads no catalogue: ```bash jupyter lab --LabApp.default_locale=en ``` or the following traitlet: ```python c.LabApp.default_locale = 'en' ``` Everyone then sees the interface in English, whatever language they had selected. To check what is installed instead of switching, report any pack whose header carries more than a plural rule: ```bash python -c " import re from jupyterlab_server.translation_utils import get_language_packs, get_language_pack ok = re.compile(r'\s*nplurals\s*=\s*\d+\s*;\s*plural\s*=[\s\-?|&=!<>+*/%:;n0-9_()]+') packs, _ = get_language_packs() for locale in packs: data, _ = get_language_pack(locale) for domain, catalog in (data or {}).items(): header = catalog.get('', {}).get('plural_forms') if header and not ok.fullmatch(header): print('SUSPECT', locale, domain, repr(header)) " ``` The command prints nothing when every catalogue is sound. A line of output names the pack to remove.

CVE-2026-102830 Affected JupyterLab Versions

3 component(s)
Fixed Versions:
4.6.44.5.110.8.4
Product / Package Ecosystem Affected Versions Fixed Version
jupyterlab
PyPI
≥ 4.6.0
< 4.6.4
4.6.4
jupyterlab
PyPI
≥ 3.0.0
< 4.5.11
4.5.11
jupyterlite-core
PyPI
< 0.8.4
0.8.4

References

Frequently Asked Questions

What is CVE-2026-102830?
CVE-2026-102830 is a security vulnerability in JupyterLab involving Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json) under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which JupyterLab versions are affected?
Affected versions include releases prior to 4.6.4, 4.5.11, 0.8.4 across affected packages: jupyterlab, jupyterlite-core.
What version fixes CVE-2026-102830?
Upgrading to 4.6.4, 4.5.11, 0.8.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is jupyterlab affected?
Yes, jupyterlab is affected in releases prior to 4.6.4, 4.5.11. Upgrade your dependency to 4.6.4, 4.5.11 or later.
Is jupyterlite-core affected?
Yes, jupyterlite-core is affected in releases prior to 0.8.4. Upgrade your dependency to 0.8.4 or later.
What is the CVSS score of CVE-2026-102830?
CVE-2026-102830 has a CVSS v3.1 base score of 6.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-102830?
CVE-2026-102830 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check PyPI dependencies for CVE-2026-102830?
Run the dependency tree command: 'pip show jupyterlab'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3jqq-pw4j-pqcj",
  "modified" : "2026-10-01T15:22:17Z",
  "published" : "2026-10-01T15:22:17Z",
  "aliases" : [ "CVE-2026-102830" ],
  "summary" : "JupyterLab: Cross-site scripting (XSS) in JupyterLab via crafted language package (jupyterlab.json)",
  "details" : "## Description\n\nA language pack ships a `Plural-Forms` header saying how the language counts, for example `nplurals=2; plural=(n != 1);`. JupyterLab turns that string into a function with `new Function`, so the header gets executed. The check that meant to keep it safe was a regular expression. The regex was anchored at the start but not at the end, so it accepted any string that began with a valid plural rule and ignored everything after it.\n\nA header such as the following passed the check, and the part after the plural rule ran in the JupyterLab page as soon as the first plural string was translated:\n\n```\nnplurals=2; plural=(n > 1); <anything here ran as JavaScript>\n```\n\nUsers are affected if all of the following are true:\n\n- they run JupyterLab 3.0.0 through 4.6.3, or an application that bundles it such as Notebook 7;\n- a language pack they did not write is installed in the environment; and\n- that language is selected, so its catalogue is loaded\n\nAn installation using the default English locale loads no catalogue and is not affected.\n\n> CVE assignment pending, GitHub CNA is experiencing severe backlog\n\n### Impact\n\nThe 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.\n\nWhat 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. The header is different because it is catalogue metadata: it travels with translation content, through the [translation pipeline](https://jupyterlab.readthedocs.io/en/latest/developer/internationalization.html) that carries strings from Crowdin into the language packs, and it is reviewed as text rather than as code. Anyone able to change a catalogue, or to publish a pack under a name someone installs, got JavaScript execution in every browser that selected that language.\n\nNote: the impact is much more limited on JupyterLite which typically does not have access to most of the surfaces that this flaw exposes.\n\n### Patches\n\nJupyterLab [`v4.6.4`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4) and [`v4.5.11`](https://github.com/jupyterlab/jupyterlab/releases/tag/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.\n\nJupyterLab 3.x reached end of life and receives no patch. Its users should move to a supported 4.x release.\n\nUsers of applications that depend on JupyterLab, such as Notebook v7+, should update `jupyterlab` package too.\n\n### Workarounds\n\nUse the English locale, which loads no catalogue:\n\n```bash\njupyter lab --LabApp.default_locale=en\n```\n\nor the following traitlet:\n\n```python\nc.LabApp.default_locale = 'en'\n```\n\nEveryone then sees the interface in English, whatever language they had selected.\n\nTo check what is installed instead of switching, report any pack whose header carries more than a plural rule:\n\n```bash\npython -c \"\nimport re\nfrom jupyterlab_server.translation_utils import get_language_packs, get_language_pack\nok = re.compile(r'\\s*nplurals\\s*=\\s*\\d+\\s*;\\s*plural\\s*=[\\s\\-?|&=!<>+*/%:;n0-9_()]+')\npacks, _ = get_language_packs()\nfor locale in packs:\n    data, _ = get_language_pack(locale)\n    for domain, catalog in (data or {}).items():\n        header = catalog.get('', {}).get('plural_forms')\n        if header and not ok.fullmatch(header):\n            print('SUSPECT', locale, domain, repr(header))\n\"\n```\n\nThe command prints nothing when every catalogue is sound. A line of output names the pack to remove.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.6.0"
      }, {
        "fixed" : "4.6.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.6.3"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlab"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "4.5.11"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 4.5.10"
    }
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "jupyterlite-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.8.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-3jqq-pw4j-pqcj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-102830"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/985a3223cd77fd4f991cd90066342a90711d70f6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/de324ae91346c713c4f5e5485f97b6e914e0f774"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/commit/f9de43dc565a1118120d466117f877a189a4ce90"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jupyterlab/jupyterlab"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-625", "CWE-79", "CWE-94" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-01T15:22:17Z",
    "nvd_published_at" : "2026-09-29T19:17:25Z"
  }
}