JupyterLab before 4.5.9 contains a stored cross-site scripting vulnerability in the Extension Manager that fails to validate URI protocols in… (CVE-2026-67338)
JupyterLab versions before 4.5.9 contain a stored cross-site scripting (XSS) vulnerability in the Extension Manager. This flaw arises from improper validation of URI protocols in package metadata URLs, allowing attackers to publish malicious PyPI packages with javascript: URLs. When users click the extension name, arbitrary JavaScript can execute within the JupyterLab origin. The vulnerability has a CVSS score of 6.1, indicating medium severity.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-67338) in JupyterLab prior to version 4.5.9 is a stored cross-site scripting issue located in the Extension Manager component. It fails to properly validate URI protocols in package metadata URLs, specifically allowing javascript: scheme URLs. Attackers can exploit this by publishing malicious PyPI packages containing such URLs in their project metadata. When a user interacts with the extension name in JupyterLab, the embedded JavaScript executes in the context of the JupyterLab origin, potentially leading to client-side code execution. The CVSS 3.1 vector indicates network attack vector, low attack complexity, no privileges required, user interaction required, scope changed, with low confidentiality and integrity impact, and no availability impact.
Potential Impact
Successful exploitation allows execution of arbitrary JavaScript code in the context of the JupyterLab origin when users click on a malicious extension name. This can lead to partial confidentiality and integrity compromise within the user's session or environment. There is no direct impact on availability. The vulnerability requires user interaction (clicking the extension name) and can be triggered remotely without privileges.
Mitigation Recommendations
A fix is available in JupyterLab version 4.5.9. Users and administrators should upgrade to version 4.5.9 or later to remediate this vulnerability. Since this is not a cloud service, manual patching is required. No vendor advisory content was provided to indicate alternative mitigations or that no action is required.
JupyterLab before 4.5.9 contains a stored cross-site scripting vulnerability in the Extension Manager that fails to validate URI protocols in… (CVE-2026-67338)
Description
JupyterLab versions before 4.5.9 contain a stored cross-site scripting (XSS) vulnerability in the Extension Manager. This flaw arises from improper validation of URI protocols in package metadata URLs, allowing attackers to publish malicious PyPI packages with javascript: URLs. When users click the extension name, arbitrary JavaScript can execute within the JupyterLab origin. The vulnerability has a CVSS score of 6.1, indicating medium severity.
CVSS v3.1
Score 6.1medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-67338) in JupyterLab prior to version 4.5.9 is a stored cross-site scripting issue located in the Extension Manager component. It fails to properly validate URI protocols in package metadata URLs, specifically allowing javascript: scheme URLs. Attackers can exploit this by publishing malicious PyPI packages containing such URLs in their project metadata. When a user interacts with the extension name in JupyterLab, the embedded JavaScript executes in the context of the JupyterLab origin, potentially leading to client-side code execution. The CVSS 3.1 vector indicates network attack vector, low attack complexity, no privileges required, user interaction required, scope changed, with low confidentiality and integrity impact, and no availability impact.
Potential Impact
Successful exploitation allows execution of arbitrary JavaScript code in the context of the JupyterLab origin when users click on a malicious extension name. This can lead to partial confidentiality and integrity compromise within the user's session or environment. There is no direct impact on availability. The vulnerability requires user interaction (clicking the extension name) and can be triggered remotely without privileges.
Mitigation Recommendations
A fix is available in JupyterLab version 4.5.9. Users and administrators should upgrade to version 4.5.9 or later to remediate this vulnerability. Since this is not a cloud service, manual patching is required. No vendor advisory content was provided to indicate alternative mitigations or that no action is required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r75g-r7w6-363h
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67338"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6e6290bf32cb7a344f5e31
Added to database: 08/01/2026, 21:18:08 UTC
Last enriched: 08/01/2026, 21:19:55 UTC
Last updated: 08/01/2026, 22:37:53 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.