Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102830 Overview
CVE-2026-102830 is a client-side JavaScript injection vulnerability in JupyterLab and JupyterLite Core caused by incomplete regular expression validation of the Plural-Forms header in third-party language packs. Affected releases include JupyterLab 3.0.0 through versions prior to 4.5.11 and 4.6.4, and JupyterLite Core 0.8.3 and earlier. A malicious language pack can append arbitrary JavaScript after a valid plural rule because the validation regex used a prefix-only match. JupyterLab then passes the accepted expression to new Function, executing the injected code in the authenticated JupyterLab origin. The default English locale is unaffected because it does not load a translation catalogue.
Critical Impact
When Jupyter Server kernels, terminals, and APIs are exposed, injected code executes with authenticated user privileges and can read or modify files and run code on the server.
Affected Products
- JupyterLab 3.0.0 up to (but not including) 4.5.11
- JupyterLab 4.6.0 up to (but not including) 4.6.4
- JupyterLite Core 0.8.3 and earlier
Discovery Timeline
- 2026-09-29 - CVE-2026-102830 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-102830
Vulnerability Analysis
The flaw lives in packages/translation/src/gettext.ts, where JupyterLab parses the Plural-Forms header from a loaded gettext catalogue. The parser uses a regular expression to whitelist characters allowed in the plural expression before passing the string to the JavaScript new Function constructor. Because the regex was anchored only at the start (^) and lacked an end-of-string anchor ($), any content appended after a valid plural rule bypassed validation. When a translation function later invoked the compiled plural rule, the appended JavaScript executed in the JupyterLab origin. This is classified as [CWE-79] cross-site scripting, but the practical impact resembles authenticated remote code execution against the Jupyter Server backing the session.
Root Cause
The validation regex ^\s*nplurals\s*=\s*\d+\s*;\s*plural\s*=[\s\-?|&=!<>+*/%:;n0-9_()]+ matched a valid prefix but did not require the entire string to conform. Trailing characters, including arbitrary JavaScript, passed validation and were compiled by new Function, producing an attacker-controlled function body.
Attack Vector
Exploitation requires a user to load a malicious or tampered third-party language pack and then trigger a plural translation lookup. The attack vector is network-based with user interaction required. Once triggered, the injected script runs with the authenticated user's session and can call Jupyter Server APIs to read files, write files, or spawn kernel processes. Impact is significantly reduced in JupyterLite because it typically lacks a Jupyter Server backend.
// Security patch in packages/translation/src/gettext.ts
// Source: https://github.com/jupyterlab/jupyterlab/commit/985a3223cd77fd4f991cd90066342a90711d70f6
// plural forms list available here http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html
// eslint-disable-next-line prefer-regex-literals
let pf_re = new RegExp(
- '^\\s*nplurals\\s*=\\s*\\d+\\s*;\\s*plural\\s*=[\\s\\-?|&=!<>+*/%:;n0-9_()]+'
+ '^\\s*nplurals\\s*=\\s*\\d+\\s*;\\s*plural\\s*=[\\s\\-?|&=!<>+*/%:;n0-9_()]+$'
);
if (!pf_re.test(pluralForm))
The fix appends the $ end-of-string anchor, forcing the entire Plural-Forms header to match the whitelist rather than only its prefix.
Detection Methods for CVE-2026-102830
Indicators of Compromise
- Third-party JupyterLab language packs installed from untrusted sources, particularly those modifying the Plural-Forms header in .po or .mo catalogues.
- Gettext catalogue files whose Plural-Forms line contains characters or tokens beyond the standard nplurals=N; plural=EXPR; pattern.
- Unexpected outbound HTTP requests or file system activity originating from an authenticated JupyterLab session immediately after a language switch.
Detection Strategies
- Scan installed language pack packages for Plural-Forms headers that do not fully conform to the whitelist regex ending with $.
- Inventory JupyterLab and JupyterLite Core versions across managed hosts and flag any release earlier than 4.5.11, 4.6.4, or 0.8.4 respectively.
- Monitor package installation activity (pip install, conda install) targeting jupyterlab-language-pack-* distributions from non-official indexes.
Monitoring Recommendations
- Log Jupyter Server API calls and correlate anomalous file read/write or kernel-execution activity with recent language pack loads.
- Alert on browser-side console errors referencing gettext.ts or plural-form parsing failures, which may indicate exploitation attempts.
- Track outbound network connections from Jupyter Server processes to identify data exfiltration following code injection.
How to Mitigate CVE-2026-102830
Immediate Actions Required
- Upgrade JupyterLab to version 4.5.11 or 4.6.4 and JupyterLite Core to 0.8.4.
- Remove any third-party language packs installed from unverified sources until they can be audited.
- Restrict language pack installation to trusted, signed distributions and require code review of catalogue files.
Patch Information
The fix is committed across three branches of the JupyterLab repository. Review the JupyterLab Security Advisory GHSA-3jqq-pw4j-pqcj, the patch commits 985a322, de324ae, and f9de43d, and the fixed releases JupyterLab v4.5.11 and JupyterLab v4.6.4.
Workarounds
- Use only the default English locale, which does not load a translation catalogue and is not affected.
- Audit installed language packs and remove any whose Plural-Forms header contains content beyond the standard nplurals=N; plural=EXPR; structure.
- Where JupyterLite is deployed without a Jupyter Server backend, exposure is limited; still upgrade to 0.8.4 to eliminate residual client-side risk.
# Upgrade to patched versions
pip install --upgrade 'jupyterlab>=4.5.11,<4.6' || \
pip install --upgrade 'jupyterlab>=4.6.4'
# For JupyterLite Core
pip install --upgrade 'jupyterlite-core>=0.8.4'
# Verify installed version
jupyter lab --version
# Audit installed language packs
pip list | grep -i 'jupyterlab-language-pack'
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

