CVE-2026-73417

jupyterlab: jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Arc...

CVE-2026-73417 is fixed in jupyterlab on 1 platform by DEBIAN-CVE-2026-73417 (version 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4), released August 25, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0075
55th percentile

jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. From 3.3.0 until 4.5.10 and 4.6.2, JupyterLab allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor. In packages/notebook-extension/schema/tracker.json and packages/notebook-extension/src/index.ts, the sideBySideLeftMarginOverride and sideBySideRightMarginOverride settings are not properly validated before being inserted into style content, allowing a crafted settings file to contain instructions that execute as code instead of only changing display preferences. A user can import the malicious file, or an attacker with access to a shared settings location can plant an overrides.json that is applied automatically. The embedded code runs with the affected user's access and can read or modify notebooks and files and run code through the notebook server, including on a connected kernel. This issue is fixed in versions 4.5.10 and 4.6.2.

Where it's fixed

ProductFixed inFixReleased
Linux
jupyterlab · Debian 14 4.4.10+ds1+~3.1.0+~0.16.6+~cs1.4.4-4 DEBIAN-CVE-2026-73417 Aug 25, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.