JupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)
JupyterLab versions from 3.3.0 up to but not including 4.5.10, and from 4.6.0 up to but not including 4.6.2, contain a cross-site scripting (XSS) vulnerability via crafted overrides.json settings files. This vulnerability arises because certain settings are not properly validated before being inserted into style content, allowing malicious code execution when a user imports a crafted settings file or when an attacker plants such a file in a shared location. The embedded code executes with the affected user's privileges and can read or modify notebooks, files, and execute code on the notebook server and connected kernels. The issue is fixed in versions 4.5.10 and 4.6.2.
AI Analysis
Technical Summary
JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In affected versions (>=3.3.0 <4.5.10 and >=4.6.0 <4.6.2), the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content. This improper validation enables a crafted settings file to contain instructions that execute as code rather than just changing display preferences. A user importing such a malicious file or an attacker placing it in a shared settings location can trigger execution of embedded code with the user's privileges, potentially reading/modifying notebooks and files and running code on the notebook server and connected kernels. The vulnerability is addressed in versions 4.5.10 and 4.6.2.
Potential Impact
Exploitation of this vulnerability allows code execution in the context of the affected user, enabling reading and modification of notebooks and files, and execution of arbitrary code on the notebook server and connected kernels. This can lead to unauthorized access and control over user data and computational resources within JupyterLab environments.
Mitigation Recommendations
A fix is available in JupyterLab versions 4.5.10 and 4.6.2. Users and administrators should upgrade affected installations to one of these versions or later to remediate this vulnerability. Until patched, users should avoid importing untrusted overrides.json settings files and restrict access to shared settings locations to trusted parties only.
JupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)
Description
JupyterLab versions from 3.3.0 up to but not including 4.5.10, and from 4.6.0 up to but not including 4.6.2, contain a cross-site scripting (XSS) vulnerability via crafted overrides.json settings files. This vulnerability arises because certain settings are not properly validated before being inserted into style content, allowing malicious code execution when a user imports a crafted settings file or when an attacker plants such a file in a shared location. The embedded code executes with the affected user's privileges and can read or modify notebooks, files, and execute code on the notebook server and connected kernels. The issue is fixed in versions 4.5.10 and 4.6.2.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In affected versions (>=3.3.0 <4.5.10 and >=4.6.0 <4.6.2), the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content. This improper validation enables a crafted settings file to contain instructions that execute as code rather than just changing display preferences. A user importing such a malicious file or an attacker placing it in a shared settings location can trigger execution of embedded code with the user's privileges, potentially reading/modifying notebooks and files and running code on the notebook server and connected kernels. The vulnerability is addressed in versions 4.5.10 and 4.6.2.
Potential Impact
Exploitation of this vulnerability allows code execution in the context of the affected user, enabling reading and modification of notebooks and files, and execution of arbitrary code on the notebook server and connected kernels. This can lead to unauthorized access and control over user data and computational resources within JupyterLab environments.
Mitigation Recommendations
A fix is available in JupyterLab versions 4.5.10 and 4.6.2. Users and administrators should upgrade affected installations to one of these versions or later to remediate this vulnerability. Until patched, users should avoid importing untrusted overrides.json settings files and restrict access to shared settings locations to trusted parties only.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pppj-hq3g-57pj
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a616bcb9c2644c7f80dbc2c
Added to database: 07/23/2026, 01:18:03 UTC
Last enriched: 08/19/2026, 14:07:44 UTC
Last updated: 09/05/2026, 02:14:07 UTC
Views: 80
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.