CVE-2026-73417 is a high-severity cross-site scripting vulnerability in JupyterLab affecting versions 3.3.0 through 4.5.9 and 4.6.0 through 4.6.1. The flaw arises from improper validation of the notebook settings values sideBySideLeftMarginOverride and sideBySideRightMarginOverride before they are inserted into generated style content. Because these settings are intended to control display margins but are not safely constrained, a crafted settings file can inject executable instructions rather than benign presentation values. The vulnerable logic is associated with the notebook extension settings schema and implementation, including tracker schema handling and notebook extension code paths that apply the imported settings. Exploitation can occur when a user imports a malicious settings file through the Settings Editor, or when a malicious settings override is placed in a shared settings location that JupyterLab loads automatically. Once processed, the injected code executes in the context of the victim's JupyterLab session.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.