How severe is GHSA-gx64-gj6p-pc4c?

No CVSS score has been assigned to GHSA-gx64-gj6p-pc4c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gx64-gj6p-pc4c?

GHSA-gx64-gj6p-pc4c affects the following packages: jupyterlab (PyPI), jupyterlab (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-gx64-gj6p-pc4c?

Update jupyterlab to 4.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gx64-gj6p-pc4c is resolved across your whole dependency graph.

How do I detect GHSA-gx64-gj6p-pc4c in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyterlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gx64-gj6p-pc4c if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-gx64-gj6p-pc4c actively exploited in the wild?

No public exploit code has been indexed for GHSA-gx64-gj6p-pc4c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gx64-gj6p-pc4c?

GHSA-gx64-gj6p-pc4c has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gx64-gj6p-pc4c?

GHSA-gx64-gj6p-pc4c is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-gx64-gj6p-pc4c published, and has it been updated?

GHSA-gx64-gj6p-pc4c was published on July 22, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

JupyterLab: Image viewer allows XSS when opening malicious image in new browser tabGHSA-gx64-gj6p-pc4c

Fix: jupyterlab/jupyterlab#19184

GHSA-gx64-gj6p-pc4c is a Cross-site Scripting (XSS) vulnerability in jupyterlab. A fix is available for jupyterlab — see the affected versions and patch details below.

Also known asBIT-jupyterlab-2026-73415CVE-2026-73415PYSEC-2026-3671

Published

Jul 22, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gx64-gj6p-pc4c.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍jupyterlab🐍jupyterlab

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

This vulnerability allows for arbitrary code execution.

Patches

JupyterLab v4.6.2 and v4.5.10 contain the patch.

Workarounds

Disable the image viewer plugin:

jupyter labextension disable @jupyterlab/imageviewer-extension:plugin

Confirm with:

jupyter labextension list

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`jupyterlab`	≥ 4.6.0&&< 4.6.2	4.6.2`pip install --upgrade 'jupyterlab==4.6.2'`
🐍PyPI	`jupyterlab`	all versions	4.5.10`pip install --upgrade 'jupyterlab==4.5.10'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyterlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jupyterlab to 4.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gx64-gj6p-pc4c is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as having an Important impact because successful exploitation permits arbitrary code execution within the context of the running JupyterLab server process, potentially compromising the user's workbench environment. Within Red Hat OpenShift AI (RHOAI), containerized workbench images provide…

Product	Fixed in	Advisory
Red Hat OpenShift AI 2.25	`rhoai/odh-feature-server-rhel9:1787315684`	RHSA-2026:65126
Red Hat OpenShift AI 2.25	`rhoai/odh-feature-server-rhel9:1792148523`	RHSA-2026:87410
Red Hat OpenShift AI 3.3	`rhoai/odh-feature-server-rhel9:1789745631`	RHSA-2026:73987
Red Hat OpenShift AI 3.4	`rhoai/odh-feature-server-rhel9:1791863220`	RHSA-2026:84734

Frequently Asked Questions

JupyterLab's image viewer allows for cross-site scripting (XSS) when a specially-crafted image file is opened through the image viewer and then opened in a new tab. This XSS issue can be used to cause remote code execution (RCE) on the JupyterLab server. ### Impact This vulnerability allows for arbitrary code execution. ### Patches JupyterLab [`v4.6.2`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.6.2) and [`v4.5.10`](https://github.com/jupyterlab/jupyterlab/releases/tag/v4.5.10) contain the patch. ### Workarounds Disable the image viewer plugin: ``` jupyter labextension dis

O3 Security · Impact-Aware SCA

Is GHSA-gx64-gj6p-pc4c in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works