What is GHSA-GX64-GJ6P-PC4C?

GHSA-GX64-GJ6P-PC4C is a high-severity cross-site scripting (XSS) vulnerability in jupyterlab (pip), affecting versions >= 4.6.0, <= 4.6.1. It is fixed in 4.6.2, 4.5.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of jupyterlab are affected by GHSA-GX64-GJ6P-PC4C?

jupyterlab (pip) versions >= 4.6.0, <= 4.6.1 is affected.

Is there a fix for GHSA-GX64-GJ6P-PC4C?

Yes. GHSA-GX64-GJ6P-PC4C is fixed in 4.6.2, 4.5.10. Upgrade to this version or later.

Is GHSA-GX64-GJ6P-PC4C exploitable, and should I be worried?

Whether GHSA-GX64-GJ6P-PC4C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-GX64-GJ6P-PC4C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-GX64-GJ6P-PC4C?

Upgrade: jupyterlab to 4.6.2 or later, jupyterlab to 4.5.10 or later.

GHSA-GX64-GJ6P-PC4C in jupyterlab

Q: Which versions of jupyterlab are affected by GHSA-GX64-GJ6P-PC4C?

jupyterlab (pip) versions >= 4.6.0, <= 4.6.1 is affected.

Q: Is there a fix for GHSA-GX64-GJ6P-PC4C?

Yes. GHSA-GX64-GJ6P-PC4C is fixed in 4.6.2, 4.5.10. Upgrade to this version or later.

Q: Is GHSA-GX64-GJ6P-PC4C exploitable, and should I be worried?

Whether GHSA-GX64-GJ6P-PC4C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-GX64-GJ6P-PC4C is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-GX64-GJ6P-PC4C?

Upgrade: jupyterlab to 4.6.2 or later, jupyterlab to 4.5.10 or later.

Summary

JupyterLab: Image viewer allows XSS when opening malicious image in new browser tab

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.

Workarounds

Disable the image viewer plugin:

jupyter labextension disable @jupyterlab/imageviewer-extension:plugin

Confirm with:

jupyter labextension list

Impact

This vulnerability allows for arbitrary code execution.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

jupyterlab (>= 4.6.0, <= 4.6.1) jupyterlab (<= 4.5.9)

Security releases

jupyterlab → 4.6.2 (pip) jupyterlab → 4.5.10 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is GHSA-GX64-GJ6P-PC4C? GHSA-GX64-GJ6P-PC4C is a high-severity cross-site scripting (XSS) vulnerability in jupyterlab (pip), affecting versions >= 4.6.0, <= 4.6.1. It is fixed in 4.6.2, 4.5.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of jupyterlab are affected by GHSA-GX64-GJ6P-PC4C? jupyterlab (pip) versions >= 4.6.0, <= 4.6.1 is affected.
Is there a fix for GHSA-GX64-GJ6P-PC4C? Yes. GHSA-GX64-GJ6P-PC4C is fixed in 4.6.2, 4.5.10. Upgrade to this version or later.
Is GHSA-GX64-GJ6P-PC4C exploitable, and should I be worried? Whether GHSA-GX64-GJ6P-PC4C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-GX64-GJ6P-PC4C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-GX64-GJ6P-PC4C?
- Upgrade jupyterlab to 4.6.2 or later
- Upgrade jupyterlab to 4.5.10 or later

Other vulnerabilities in jupyterlab

CVE-IDSeverityPackage summary

GHSA-PPPJ-HQ3G-57PJHighjupyterlab: JupyterLab: Cross-site scripting (XSS) via crafted settings file (`overrides.json`)GHSA-89VP-JRXV-24W8Mediumjupyterlab: JupyterLab: PyPI extension blocklist package-name canonicalization bypass GHSA-H5V5-8746-G7MMMediumjupyterlab: JupyterLab PluginManager lock-rule enforcement bypass GHSA-WHVH-WF3X-G77JLowjupyterlab: JupyterLab: Allowlist/blocklist check in `PyPIExtensionManager.install()` not enforced for direct callers (missing `await`)GHSA-VMHF-C436-HXJ4Mediumjupyterlab: JupyterLab: Stored XSS in extension manager through package metadata unsanitized URI protocol