JupyterLab before 4.5.9 contains a stored cross-site scripting vulnerability in the Extension Manager that fails to validate URI protocols in package metadata URLs. Attackers can publish malicious PyPI packages with javascript: URLs in project metadata that execute arbitrary JavaScript in the JupyterLab origin when users click the extension name.
CVE-2026-67338
Score 6.1 from GitHub Security Advisory published 2026-08-01. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 1, 2026
Last Modified
August 3, 2026
Advisory Details (4)
Auto-updated Aug 1, 2026JupyterLab before 4.5.9 Stored XSS via Extension Manager | Advisories | VulnCheck
https://www.vulncheck.com/advisories/jupyterlab-before-stored-xss-via-extension-managercommit d5d961f6e10a (jupyterlab/jupyterlab)
Fix landed in jupyterlab/jupyterlab commit d5d961f6e10a — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/commit/d5d961f6e10a6442dddbf94d9a976b3897055a12commit 4e61e07d0a91 (jupyterlab/jupyterlab)
Fix landed in jupyterlab/jupyterlab commit 4e61e07d0a91 — awaiting tagged release
https://github.com/jupyterlab/jupyterlab/commit/4e61e07d0a91145b53fbf96ac74b0387f6bc51f6Stored XSS in extension manager through package metadata unsanitized URI protocol · Advisory · jupyterlab/jupyterlab · GitHub
https://github.com/jupyterlab/jupyterlab/security/advisories/GHSA-vmhf-c436-hxj4Vendor Advisories for CVE-2026-67338(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (26 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (26 versions) | — | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jupyterlab | 0.0.1 ... 4.5.8 (586 versions) | 4.5.9 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 60× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 10:35 UTCEG score recompute
- 2026-08-20 10:35 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:42 UTCEG score recompute
- 2026-08-19 09:42 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 08:41 UTCEG score recompute
- 2026-08-18 08:41 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:42 UTCEG score recompute
- 2026-08-17 07:42 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:50 UTCEG score recompute
- 2026-08-16 06:50 UTCGHSA enrichment
- 2026-08-15 05:58 UTCEG score recompute
- 2026-08-15 05:58 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 05:05 UTCEG score recompute
- 2026-08-14 05:05 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 04:12 UTCEG score recompute
- 2026-08-13 04:12 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 03:20 UTCEG score recompute
Show 35 moreShow fewer
- 2026-08-12 03:20 UTCGHSA enrichment
- 2026-08-11 02:27 UTCEG score recompute
- 2026-08-11 02:27 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 01:35 UTCEG score recompute
- 2026-08-10 01:35 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 00:43 UTCEG score recompute
- 2026-08-09 00:43 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 23:51 UTCEG score recompute
- 2026-08-07 23:51 UTCGHSA enrichment
- 2026-08-06 22:58 UTCEG score recompute
- 2026-08-06 22:58 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 22:06 UTCEG score recompute
- 2026-08-05 22:06 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 21:14 UTCEG score recompute
- 2026-08-04 21:13 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 20:20 UTCEG score recompute
- 2026-08-03 20:20 UTCGHSA enrichment
- 2026-08-03 20:14 UTCEG score recompute
- 2026-08-03 20:14 UTCGHSA enrichment
- 2026-08-03 15:06 UTCEG score recompute
- 2026-08-03 15:06 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 14:12 UTCEG score recompute
- 2026-08-02 14:12 UTCGHSA enrichment
- 2026-08-01 13:19 UTCEG score recompute
- 2026-08-01 12:44 UTCEG score recompute
- 2026-08-01 12:42 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-67338?
When was CVE-2026-67338 disclosed?
Is CVE-2026-67338 actively exploited?
What is the CVSS score of CVE-2026-67338?
How do I remediate CVE-2026-67338?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67338
Is Your Infrastructure Affected by CVE-2026-67338?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.