JupyterLab vulnerable to SXSS in Markdown Preview

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-22420: 0.57% estimated exploitation activity in the next 30 days; percentile 47.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The vulnerability depends on user interaction by opening a malicious notebook with Markdown cells, or Markdown file using JupyterLab preview feature. A malicious user can access any data that the attacked user has access to as well as perform arbitrary requests acting as the attacked user. Patches JupyterLab v4.0.11 was patched. Workarounds Users can either disable the table of contents extension by running: References Vulnerability reported via the bug bounty program sponsored by the European Commission and hosted on the Intigriti platform.

Published by the source

19 Jan 2024, 20:24 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4m77-cmpx-vjc4

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4m77-cmpx-vjc4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-22420

Advisory: JupyterLab vulnerable to SXSS in Markdown Preview
IDs: CVE-2024-22420, GHSA-4m77-cmpx-vjc4
Record: https://patchnext.com/advisories/cve-2024-22420 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jupyterlab 4.0.11; notebook 7.0.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI jupyterlab: affected >= 4.0.0, <= 4.0.10; fixed in 4.0.11
- PyPI notebook: affected >= 7.0.0, <= 7.0.6; fixed in 7.0.7

## Suggested inspection (read-only)
- `python -m pip show jupyterlab`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show notebook`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jupyterlab, notebook.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4m77-cmpx-vjc4 (OSV record GHSA-4m77-cmpx-vjc4 lists affected ranges: PyPI jupyterlab >=4.0.0 =7.0.0 <7.0.7 (fixed))
- Verified: https://github.com/advisories/GHSA-4m77-cmpx-vjc4 (GitHub-reviewed advisory GHSA-4m77-cmpx-vjc4 lists affected ranges: PyPI jupyterlab >=4.0.0 =7.0.0 <=7.0.6)

Commands are suggestions: review each one before running it.