Advisory

GHSA-vmhf-c436-hxj4

Also known as: BIT-jupyterlab-2026-67338, CVE-2026-67338

Summary

JupyterLab: Stored XSS in extension manager through package metadata unsanitized URI protocol

Details

A malicious PyPI package can place a javascript: URL in its [project.urls] metadata. JupyterLab's Extension Manager renders this as the extension's home-page link without validating the protocol, so a user who clicks the extension name executes attacker-controlled JavaScript in the JupyterLab origin.

Details

One of the PyPI package's URL (jupyterlab/extensions/pypi.py) is copied straight into the homepage_url rendered by the frontend in packages/extensionmanager/src/widget.tsx#L77-L88.

best_guess_home_url = (
    homepage_url            # home_page / [project.urls] Homepage
    or data.get("project_url")
    or data.get("package_url")
    or documentation_url    # docs_url / [project.urls] Documentation
    or source_url           # [project.urls] Source Code
    or bug_tracker_url      # bugtrack_url / [project.urls] Bug Tracker
)

# homepage_url=best_guess_home_url
{entry.homepage_url ? (
  <a href={entry.homepage_url} target="_blank" rel="noopener noreferrer" ...>
    {entry.name}
  </a>
) : ( <div>{entry.name}</div> )}

Impact

An attacker needs to publish a package to PyPI (no access to the target). When the package appears in a victim's extension manager list and the victim clicks the extension name, the payload runs in the JupyterLab origin.

Preconditions: Extension Manager enabled with the default PyPI source, the malicious package appears in the victim's list/search results.

Patches
Patched in 4.5.9, commits 4e61e07 and d5d961f

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-19 15:11 UTC
Modified
2026-10-14 11:11 UTC

Affected packages and fixes

jupyterlab

PyPI · All systems

Affected

  • introduced 0, fixed 4.5.9 (ecosystem)

Fixed versions

4.5.9

Fix

  • Fixed version 4.5.9
    pip install --upgrade jupyterlab==4.5.9

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences