Stored XSS via unsanitized package metadata URI
Published Aug 1, 2026 · Updated Aug 1, 2026
Stored XSS in the Extension Manager in Project Jupyter JupyterLab before 4.5.9 allows remote attackers to run script via package metadata. The PyPI backend copies a package project URL into homepage_url, and widget.tsx renders it as an href without restricting the javascript protocol. Execution requires the default PyPI-backed Extension Manager to show the package and a user to click its extension name; the script runs in the JupyterLab origin.
Summary
What happened
Stored XSS in the Extension Manager in Project Jupyter JupyterLab before 4.5.9 allows remote attackers to run script via package metadata. The PyPI backend copies a package project URL into homepage_url, and widget.tsx renders it as an href without restricting the javascript protocol. Execution requires the default PyPI-backed Extension Manager to show the package and a user to click its extension name; the script runs in the JupyterLab origin.
The record
- CVE
- CVE-2026-67338
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Project Jupyter
- Product
- JupyterLab
- Classifications
- CWE-84, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.5.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo