CVE-2026-73417
JupyterLab settings import allows code execution via crafted overrides.json.
Is CVE-2026-73417 being exploited?
Not confirmed. CVE-2026-73417 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-73417?
CVE-2026-73417 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73417?
Yes. A fix has been recorded for CVE-2026-73417. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73417 affect?
CVE-2026-73417 affects JupyterLab >=3.3.0 and <4.5.10, JupyterLab 4.6.0-4.6.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73417?
Upgrade to JupyterLab 4.5.10 or 4.6.2; avoid importing untrusted settings and remove shared malicious overrides.json.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malicious overrides.json can execute code as the user, read/modify notebooks/files and run code on the notebook server/kernel.
Immediate action required
- affected>= 3.3.0 and < 4.5.10
- affected>= 4.6.0 and < 4.6.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.