EUVD-2026-57535
GHSA-gx64-gj6p-pc4c
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-delivered SVG requires active two-step user interaction (AC:H, UI:R); XSS crosses to server kernel API, constituting a scope change (S:C); full confidentiality and integrity compromise on server, low availability impact.
Primary rating from Vendor (github).
CVSS VectorVendor: github
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
4Blast Radius
ecosystem impact- 5 pypi packages depend on jupyterlab (2 direct, 3 indirect)
Ecosystem-wide dependent count for version 4.6.0.
DescriptionCVE.org
jupyterlab is an extensible environment for interactive and reproducible computing, based on the Jupyter Notebook Architecture. Prior to 4.5.10 and 4.6.2, in packages/imageviewer/src/widget.ts, JupyterLab's ImageViewer uses URL.createObjectURL for a specially crafted SVG image and revokes the blob URL too early, allowing the image to retain an executable same-origin context when it is opened through the image viewer and then opened in a new browser tab. The resulting cross-site scripting can be used to execute arbitrary code on the JupyterLab server. This issue is fixed in versions 4.5.10 and 4.6.2.
AnalysisAI
JupyterLab's ImageViewer component escalates a blob URL lifecycle bug into server-side remote code execution - a specially crafted SVG opened in the ImageViewer retains an executable same-origin context after its blob URL is prematurely revoked, and when the victim opens that image in a new browser tab, embedded JavaScript executes within the JupyterLab server's origin. That same-origin privilege grants direct access to JupyterLab's kernel execution API, turning a browser-side XSS into full RCE on the JupyterLab server. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Three conditions must simultaneously hold: (1) JupyterLab version must be <= 4.5.9 or 4.6.0-4.6.1; (2) the ImageViewer plugin (@jupyterlab/imageviewer-extension:plugin) must be enabled - it is enabled by default in all affected versions, so no non-default configuration is required on the server side; and (3) the victim must perform two active steps: first open the malicious SVG through the ImageViewer, then manually open it in a new browser tab. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 7.5 (AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:L) accurately captures the two-part tension of this vulnerability: the attack complexity is high because exploitation requires the victim to perform two distinct actions (open the SVG in ImageViewer, then explicitly open it in a new browser tab), yet the downstream impact is severe - VC:H and VI:H reflect full confidentiality and integrity compromise of the JupyterLab server. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker operating in a shared JupyterHub environment uploads a specially crafted SVG file to a shared dataset directory or sends it via a notebook attachment. A data scientist opens the file through JupyterLab's ImageViewer (the default handler for image files) and, wanting a closer look, right-clicks and opens it in a new browser tab - a routine workflow step. … |
| Remediation | Upgrade JupyterLab to v4.5.10 (for installations on the 4.5.x branch) or v4.6.2 (for the 4.6.x branch) - both are vendor-confirmed patched releases referenced at the GitHub releases page and backed by pull requests #19184, #19185, and #19186. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: identify all JupyterLab instances across your organization and document current versions to determine exposure scope. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allVendor StatusVendor
SUSE
Severity: ModerateShare
External POC / Exploit Code
Leaving vuln.today