Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73417

Cross-Site Scripting (XSS) in jupyterlab (CVE-2026-73417)

Summary

Cross-site scripting in jupyterlab (CVE-2026-73417). Risk of unauthorized operations or information disclosure. Exploitable via Import. Mitigation: upgrade to 4.5.10 or later.

Original description

The description as published by the source.

JupyterLab 4.5+ allows notebook settings to be shared and applied through an overrides.json file using the Import button in the Settings Editor.

Certain notebook display settings were not properly validated before being applied. As a result, a crafted settings file could contain hidden instructions that run as code inside JupyterLab when imported, instead of only changing a display preference.

Because importing a settings file appears harmless, a user could import a file shared by another party without realizing it could do more. On multi-tenant file systems without proper permission control, another user could plant a malicious overrides.json.

CVE assignment pending, GitHub CNA is experiencing severe backlog

Impact

When a malicious settings file is applied, the embedded code runs with the same access as the affected user. This could allow an attacker to read or modify that user's notebooks and files, and to run code on the user's behalf through the notebook server, including on any connected kernel.

User Interaction vs Privileges Required

Write access to a loaded settings location

If an attacker can write to a directory JupyterLab loads settings from (e.g. on shared or multi-tenant file system), they could place a crafted overrides.json that is applied to another user automatically at startup. This requires high privilages but no action by the victim.

User-imported settings file

A user can import a crafted overrides.json through th…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73417 has been found in jupyterlab.
Attackers can target a specific entry point like Import over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jupyterlab to 4.5.10 or later.
If unsure, ask your IT team or search "jupyterlab CVE-2026-73417" on the vendor's site.

CVE-2026-73417 (jupyterlab) — CWE-79
Attack surface: Import
Patched: 4.5.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in jupyterlab. Attackers reach the vulnerable code path via Import.

📍 Affected scope

Check the vendor advisory for the affected versions of jupyterlab. Attack surface: Import.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.5.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jupyterlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'jupyterlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で jupyterlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade jupyterlab to 4.5.10

    ステージング環境で 4.5.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip jupyterlab
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.10"}]}]
Bitnami jupyterlab
[{"type":"SEMVER","events":[{"introduced":"3.3.0"},{"fixed":"4.5.10"},{"introduced":"4.6.0"},{"fixed":"4.6.2"}]}]
PyPI jupyterlab
[{"type":"ECOSYSTEM","events":[{"introduced":"3.3.0"},{"fixed":"4.5.10"},{"introduced":"4.6.0"},{"fixed":"4.6.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details