JupyterLab versions 3.0.0 through 4.5.10 and 4.6.0 through 4.6.3, plus JupyterLite Core 0.8.3 and earlier, evaluate the Plural-Forms header of a third-party language pack with new Function. A weak prefix-only regex lets an attacker append arbitrary JavaScript that runs in the authenticated JupyterLab origin. Where a Jupyter Server is exposed, that script can call authenticated kernel, terminal and file APIs, which gives an attacker file access and code execution on the notebook host. Exploitation is hard to trigger: it needs a victim to install and select a malicious or compromised language pack. The CVSS is 6.8, EPSS is low at 0.26% (83rd percentile), there is no public exploit or Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. Still, the package has 1,892 dependents and 41 other CVEs, and data science workstations often hold credentials, datasets and cloud keys. Upgrade to JupyterLab 4.5.11 or 4.6.4 (JupyterLite Core 0.8.4) and allow only vetted language packs.
What is the risk?
Medium overall. Exploitation needs an attacker to place a crafted language pack in front of a user who then selects that locale (high complexity, user interaction required). The default English locale is not affected. Once triggered, the impact is high for confidentiality and integrity, because the injected code runs with the user's authenticated session and reaches Jupyter Server APIs. There is no known active exploitation, no public PoC and no KEV listing. Risk is highest on multi-user or shared JupyterHub-style deployments, and on hosts with cloud credentials or sensitive training data. JupyterLite exposure is much lower because it usually has no server surface.
How does the attack unfold?
What systems are affected?
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade JupyterLab to 4.5.11 or 4.6.4, and JupyterLite Core to 0.8.4. 2) Until patched, stay on the default English locale and remove or do not install third-party language packs (jupyterlab-language-pack-*). 3) Install language packs only from trusted sources, and pin and hash-verify them in internal package mirrors. 4) Run Jupyter Server with token or password authentication, bind it to localhost or a VPN, and give notebook hosts least-privilege credentials. 5) For detection, inventory installed language-pack packages and review their .po or catalogue files for Plural-Forms headers with trailing content after the plural expression. Also watch for unexpected terminal or kernel starts and unusual API calls in Jupyter Server logs.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-102830?
JupyterLab versions 3.0.0 through 4.5.10 and 4.6.0 through 4.6.3, plus JupyterLite Core 0.8.3 and earlier, evaluate the Plural-Forms header of a third-party language pack with new Function. A weak prefix-only regex lets an attacker append arbitrary JavaScript that runs in the authenticated JupyterLab origin. Where a Jupyter Server is exposed, that script can call authenticated kernel, terminal and file APIs, which gives an attacker file access and code execution on the notebook host. Exploitation is hard to trigger: it needs a victim to install and select a malicious or compromised language pack. The CVSS is 6.8, EPSS is low at 0.26% (83rd percentile), there is no public exploit or Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. Still, the package has 1,892 dependents and 41 other CVEs, and data science workstations often hold credentials, datasets and cloud keys. Upgrade to JupyterLab 4.5.11 or 4.6.4 (JupyterLite Core 0.8.4) and allow only vetted language packs.
Is CVE-2026-102830 actively exploited?
No confirmed active exploitation of CVE-2026-102830 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-102830?
1) Upgrade JupyterLab to 4.5.11 or 4.6.4, and JupyterLite Core to 0.8.4. 2) Until patched, stay on the default English locale and remove or do not install third-party language packs (jupyterlab-language-pack-*). 3) Install language packs only from trusted sources, and pin and hash-verify them in internal package mirrors. 4) Run Jupyter Server with token or password authentication, bind it to localhost or a VPN, and give notebook hosts least-privilege credentials. 5) For detection, inventory installed language-pack packages and review their .po or catalogue files for Plural-Forms headers with trailing content after the plural expression. Also watch for unexpected terminal or kernel starts and unusual API calls in Jupyter Server logs.
What systems are affected by CVE-2026-102830?
This vulnerability affects the following AI/ML architecture patterns: Interactive notebook environments, Training pipelines, Shared multi-user notebook servers, Browser-based JupyterLite deployments, ML development workstations.
What is the CVSS score for CVE-2026-102830?
CVE-2026-102830 has a CVSS v3.1 base score of 6.8 (MEDIUM). The EPSS exploitation probability is 0.26%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0010.001AI SoftwareAML.T0011.001Malicious PackageAML.T0037Data from Local SystemAML.T0050Command and Scripting InterpreterCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker publishes or compromises a language pack on PyPI, or tampers with a pack hosted on an internal mirror, and embeds JavaScript after a valid plural rule in its Plural-Forms header. A data scientist installs the pack and switches the interface language. When JupyterLab loads the catalogue and translates a plural string, the payload runs in the authenticated origin. It calls the Jupyter Server contents and terminal APIs to steal cloud credentials and training data, drops a backdoor notebook or startup script, and opens a kernel for further code execution on the ML workstation.
Weaknesses (CWE)
CWE-625Permissive Regular ExpressionPrimaryCWE-79Improper Neutralization of Input During Web Page GenerationPrimaryCWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')PrimaryCWE-94Improper Control of Generation of CodePrimaryCWE-94Improper Control of Generation of Code ('Code Injection')PrimaryCWE-79Improper Neutralization of Input During Web Page GenerationCWE-94Improper Control of Generation of CodeCWE-625 — Permissive Regular Expression: The product uses a regular expression that does not sufficiently restrict the set of allowed values.
- [Implementation] When applicable, ensure that the regular expression marks beginning and ending string patterns, such as "/^string$/" for Perl.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NReferences
- github.com/advisories/GHSA-3jqq-pw4j-pqcj
- nvd.nist.gov/vuln/detail/CVE-2026-102830
- github.com/jupyterlab/jupyterlab/commit/985a3223cd77fd4f991cd90066342a90711d70f6
- github.com/jupyterlab/jupyterlab/commit/de324ae91346c713c4f5e5485f97b6e914e0f774
- github.com/jupyterlab/jupyterlab/commit/f9de43dc565a1118120d466117f877a189a4ce90
- github.com/jupyterlab/jupyterlab/releases/tag/v4.5.11
- github.com/jupyterlab/jupyterlab/releases/tag/v4.6.4
- github.com/jupyterlab/jupyterlab/security/advisories/GHSA-3jqq-pw4j-pqcj
Timeline
Related Vulnerabilities
CVE-2023-2557410.0JupyterHub LTI13: JWT forgery enables full auth bypass
Same package: jupyterCVE-2024-3970010.0JupyterLab extension-template: CI workflow RCE
Same package: jupyterCVE-2026-441809.8Jupyter Enterprise Gateway: root privilege bypass in Kubernetes
Same package: jupyterCVE-2026-235379.1Feast: unauth file write to RCE via /save-document
Same package: jupyterCVE-2026-545279.0jupyterlab-git: stored XSS escalates to full RCE
Same package: jupyter